Linux 2.6.29
Subsystems (11)
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Jens AxboeQuoted 8 lines · Jens Axboe
Quoted 7 lines · Linus Torvalds
Quoted 3 lines · Ric Wheeler
The question is really what we do when you have a storage device in your box with a volatile write cache that does support flush or fua or similar.
Quoted 7 lines
Quoted 1 line
Ok. Then you are talking about a different case - not EOPNOTSUPP.
So here's a test patch that attempts to just ignore such a failure to flush the caches. It will still flag the bio as
BIO_EOPNOTSUPP, but that's merely maintaining the information in case the caller does want to see if that barrier failed or not. It may not actually be useful, in which case we can just kill that flag.
Updated version, the previous missed most of the buffer_eopnotsupp() checking. So this one also gets rid of the file system retry logic. Thanks to gfs2 Steve for pointing out that I missed gfs2, made me realize that I missed a lot more as well.
block/blk-barrier.c | 8 ++------ block/blk-settings.c | 13 +++++++++++++ block/ioctl.c | 4 +--- fs/bio.c | 12 +++++++++++- fs/btrfs/disk-io.c | 5 ----- fs/btrfs/extent_io.c | 9 ++------- fs/buffer.c | 23 ++--------------------- fs/fat/misc.c | 5 +---- fs/gfs2/log.c | 18 ++++++------------ fs/jbd2/commit.c | 22 ---------------------- fs/reiserfs/journal.c | 15 --------------- fs/xfs/linux-2.6/xfs_aops.c | 1 - include/linux/blkdev.h | 2 ++ include/linux/buffer_head.h | 2 -- 14 files changed, 40 insertions(+), 99 deletions(-)commit 74e725b7f2e5f3f073abe84c5823026a6f1e33ce
---
Author: Jens Axboe <[email protected]> Date: Tue Mar 31 19:00:53 2009 +0200
barrier: Don't return -EOPNOTSUPP to the caller if the device does not support barriers
The caller cannot really do much about the situation anyway. Instead log a warning if this is the first such failed barrier we see, so that the admin can look into whether this poses a data integrity problem or not.
block/blk-barrier.c +2 -6
@@ -338,9 +338,7 @@ int blkdev_issue_flush(struct block_device *bdev, sector_t *error_sector) *error_sector = bio->bi_sector; ret =0 ; -if (bio_flagged (bio,BIO_EOPNOTSUPP )) - ret = -EOPNOTSUPP ; -else if (!bio_flagged (bio,BIO_UPTODATE )) +if (!bio_flagged (bio,BIO_UPTODATE )) ret = -EIO ;bio_put (bio);
@@ -408,9 +406,7 @@ int blkdev_issue_discard(struct block_device *bdev,submit_bio (DISCARD_BARRIER , bio);/* Check if it failed immediately */ -if (bio_flagged (bio,BIO_EOPNOTSUPP )) - ret = -EOPNOTSUPP ; -else if (!bio_flagged (bio,BIO_UPTODATE )) +if (!bio_flagged (bio,BIO_UPTODATE )) ret = -EIO ;bio_put (bio); }
block/blk-settings.c +13 -0
@@ -463,6 +463,19 @@ void blk_queue_update_dma_alignment(struct request_queue *q, int mask) }EXPORT_SYMBOL (blk_queue_update_dma_alignment); +void blk_queue_set_noflush (struct block_device *bdev) +{ +struct request_queue *q =bdev_get_queue (bdev); +char b[BDEVNAME_SIZE ]; + +if (test_and_set_bit (QUEUE_FLAG_NOFLUSH , &q->queue_flags)) +return ; + +printk (KERN_ERR "Device %s does not appear to honor cache flushes. " +"This may mean that file system ordering guarantees " +"are not met." ,bdevname (bdev, b)); +} +static int __init blk_settings_init (void ) { blk_max_low_pfn = max_low_pfn -1 ;
block/ioctl.c +1 -3
@@ -166,9 +166,7 @@ static int blk_ioctl_discard(struct block_device *bdev, uint64_t start,wait_for_completion (&wait); -if (bio_flagged (bio,BIO_EOPNOTSUPP )) - ret = -EOPNOTSUPP ; -else if (!bio_flagged (bio,BIO_UPTODATE )) +if (!bio_flagged (bio,BIO_UPTODATE )) ret = -EIO ;bio_put (bio); }
fs/bio.c +11 -1
@@ -1380,7 +1380,17 @@ void bio_check_pages_dirty(struct bio *bio)**/ void bio_endio (struct bio *bio,int error) { -if (error) +/* +* Special case here - hide the -EOPNOTSUPP from the driver or +* block layer, dump a warning the first time this happens so that +* the admin knows that we may not provide the ordering guarantees +* that are needed. Don't clear the uptodate bit. +*/ +if (error == -EOPNOTSUPP &&bio_barrier (bio)) { +set_bit (BIO_EOPNOTSUPP , &bio->bi_flags); +blk_queue_set_noflush (bio->bi_bdev); + error =0 ; + }else if (error)clear_bit (BIO_UPTODATE , &bio->bi_flags);else if (!test_bit (BIO_UPTODATE , &bio->bi_flags)) error = -EIO ;
fs/btrfs/disk-io.c +0 -5
@@ -1951,11 +1951,6 @@ static void btrfs_end_buffer_write_sync(struct buffer_head *bh, int uptodate)if (uptodate) {set_buffer_uptodate (bh); }else { -if (!buffer_eopnotsupp (bh) &&printk_ratelimit ()) { -printk (KERN_WARNING "lost page write due to " -"I/O error on %s\n" , -bdevname (bh->b_bdev, b)); - }/* note, we dont' set_buffer_write_io_error because we have * our own ways of dealing with the IO errors */
fs/btrfs/extent_io.c +2 -7
@@ -1834,7 +1834,6 @@ extent_bio_alloc(struct block_device *bdev, u64 first_sector, int nr_vecs,static int submit_one_bio (int rw,struct bio *bio,int mirror_num,unsigned long bio_flags) { -int ret =0 ;struct bio_vec *bvec = bio->bi_io_vec + bio->bi_vcnt -1 ;struct page *page = bvec->bv_page;struct extent_io_tree *tree = bio->bi_private;
@@ -1846,17 +1845,13 @@ static int submit_one_bio(int rw, struct bio *bio, int mirror_num, bio->bi_private =NULL ; -bio_get (bio); -if (tree->ops && tree->ops->submit_bio_hook) tree->ops->submit_bio_hook (page->mapping->host, rw, bio, mirror_num, bio_flags);else submit_bio (rw, bio); -if (bio_flagged (bio,BIO_EOPNOTSUPP )) - ret = -EOPNOTSUPP ; -bio_put (bio); -return ret; + +return 0 ; } static int submit_extent_page(int rw, struct extent_io_tree *tree,
fs/buffer.c +2 -21
@@ -147,17 +147,9 @@ void end_buffer_read_sync(struct buffer_head *bh, int uptodate)void end_buffer_write_sync (struct buffer_head *bh,int uptodate) { -char b[BDEVNAME_SIZE ]; -if (uptodate) {set_buffer_uptodate (bh); }else { -if (!buffer_eopnotsupp (bh) && !quiet_error (bh)) { -buffer_io_error (bh); -printk (KERN_WARNING "lost page write due to " -"I/O error on %s\n" , -bdevname (bh->b_bdev, b)); - }set_buffer_write_io_error (bh);clear_buffer_uptodate (bh); }
@@ -2828,7 +2820,7 @@ static void end_bio_bh_io_sync(struct bio *bio, int err)if (err == -EOPNOTSUPP ) {set_bit (BIO_EOPNOTSUPP , &bio->bi_flags); -set_bit (BH_Eopnotsupp, &bh->b_state); + err =0 ; }if (unlikely (test_bit (BIO_QUIET ,&bio->bi_flags)))
@@ -2841,7 +2833,6 @@ static void end_bio_bh_io_sync(struct bio *bio, int err)int submit_bh (int rw,struct buffer_head * bh) {struct bio *bio; -int ret =0 ;BUG_ON (!buffer_locked (bh));BUG_ON (!buffer_mapped (bh));
@@ -2879,14 +2870,8 @@ int submit_bh(int rw, struct buffer_head * bh) bio->bi_end_io = end_bio_bh_io_sync; bio->bi_private = bh; -bio_get (bio);submit_bio (rw, bio); - -if (bio_flagged (bio,BIO_EOPNOTSUPP )) - ret = -EOPNOTSUPP ; - -bio_put (bio); -return ret; +return 0 ; }/**
@@ -2965,10 +2950,6 @@ int sync_dirty_buffer(struct buffer_head *bh) bh->b_end_io = end_buffer_write_sync; ret =submit_bh (WRITE , bh);wait_on_buffer (bh); -if (buffer_eopnotsupp (bh)) { -clear_buffer_eopnotsupp (bh); - ret = -EOPNOTSUPP ; - }if (!ret && !buffer_uptodate (bh)) ret = -EIO ; }else {
fs/fat/misc.c +1 -4
@@ -269,10 +269,7 @@ int fat_sync_bhs(struct buffer_head **bhs, int nr_bhs)ll_rw_block (SWRITE , nr_bhs, bhs);for (i =0 ; i < nr_bhs; i++) {wait_on_buffer (bhs[i]); -if (buffer_eopnotsupp (bhs[i])) { -clear_buffer_eopnotsupp (bhs[i]); - err = -EOPNOTSUPP ; - }else if (!err && !buffer_uptodate (bhs[i])) +if (!err && !buffer_uptodate (bhs[i])) err = -EIO ; }return err;
fs/gfs2/log.c +6 -12
@@ -578,6 +578,7 @@ static void log_write_header(struct gfs2_sbd *sdp, u32 flags, int pull)struct gfs2_log_header *lh;unsigned int tail;u32 hash; +int rw; bh =sb_getblk (sdp->sd_vfs, blkno);lock_buffer (bh);
@@ -602,20 +603,13 @@ static void log_write_header(struct gfs2_sbd *sdp, u32 flags, int pull) bh->b_end_io = end_buffer_write_sync;if (test_bit (SDF_NOBARRIERS , &sdp->sd_flags)) - goto skip_barrier; + rw =WRITE ; +else + rw =WRITE_BARRIER ; +get_bh (bh); -submit_bh (WRITE_BARRIER | (1 <<BIO_RW_META ), bh); +submit_bh (rw | (1 <<BIO_RW_META ), bh);wait_on_buffer (bh); -if (buffer_eopnotsupp (bh)) { -clear_buffer_eopnotsupp (bh); -set_buffer_uptodate (bh); -set_bit (SDF_NOBARRIERS , &sdp->sd_flags); -lock_buffer (bh); -skip_barrier: -get_bh (bh); -submit_bh (WRITE_SYNC | (1 <<BIO_RW_META ), bh); -wait_on_buffer (bh); - }if (!buffer_uptodate (bh))gfs2_io_error_bh (sdp, bh);brelse (bh);
fs/jbd2/commit.c +0 -22
@@ -174,30 +174,8 @@ static int journal_wait_on_commit_record(journal_t *journal, {int ret =0 ; -retry:clear_buffer_dirty (bh);wait_on_buffer (bh); -if (buffer_eopnotsupp (bh) && (journal->j_flags &JBD2_BARRIER )) { -printk (KERN_WARNING -"JBD2: wait_on_commit_record: sync failed on %s - " -"disabling barriers\n" , journal->j_devname); -spin_lock (&journal->j_state_lock); - journal->j_flags &= ~JBD2_BARRIER ; -spin_unlock (&journal->j_state_lock); - -lock_buffer (bh); -clear_buffer_dirty (bh); -set_buffer_uptodate (bh); - bh->b_end_io = journal_end_buffer_io_sync; - - ret =submit_bh (WRITE_SYNC , bh); -if (ret) { -unlock_buffer (bh); -return ret; - } - goto retry; - } -if (unlikely (!buffer_uptodate (bh))) ret = -EIO ;put_bh (bh);/* One for getblk() */
fs/reiserfs/journal.c +0 -15
@@ -700,18 +700,6 @@ static int submit_barrier_buffer(struct buffer_head *bh)return submit_bh (WRITE_BARRIER , bh); } -static void check_barrier_completion (struct super_block *s, -struct buffer_head *bh) -{ -if (buffer_eopnotsupp (bh)) { -clear_buffer_eopnotsupp (bh); -disable_barrier (s); -set_buffer_uptodate (bh); -set_buffer_dirty (bh); -sync_dirty_buffer (bh); - } -} -#define CHUNK_SIZE 32struct buffer_chunk {struct buffer_head *bh[CHUNK_SIZE ];
@@ -1148,8 +1136,6 @@ static int flush_commit_list(struct super_block *s, }else wait_on_buffer (jl->j_commit_bh); -check_barrier_completion (s, jl->j_commit_bh); -/* If there was a write error in the journal - we can't commit this * transaction - it will be invalid and, if successful, will just end * up propagating the write error out to the filesystem. */
@@ -1313,7 +1299,6 @@ static int _update_journal_header_block(struct super_block *sb, goto sync; }wait_on_buffer (journal->j_header_bh); -check_barrier_completion (sb, journal->j_header_bh); }else { sync:set_buffer_dirty (journal->j_header_bh);
fs/xfs/linux-2.6/xfs_aops.c +0 -1
@@ -406,7 +406,6 @@ xfs_submit_ioend_bio( bio->bi_end_io = xfs_end_bio;submit_bio (WRITE , bio); -ASSERT (!bio_flagged (bio,BIO_EOPNOTSUPP ));bio_put (bio); }
include/linux/blkdev.h +2 -0
@@ -452,6 +452,7 @@ struct request_queue#define QUEUE_FLAG_NONROT 14/* non-rotational device (SSD) */ #define QUEUE_FLAG_VIRT QUEUE_FLAG_NONROT/* paravirt device */ #define QUEUE_FLAG_IO_STAT 15/* do IO stats */ +#define QUEUE_FLAG_NOFLUSH 16/* device doesn't do flushes */ #define QUEUE_FLAG_DEFAULT ((1 << QUEUE_FLAG_IO_STAT) | \ (1 << QUEUE_FLAG_CLUSTER) | \
@@ -789,6 +790,7 @@ extern int blk_execute_rq(struct request_queue *, struct gendisk *,extern void blk_execute_rq_nowait (struct request_queue *,struct gendisk *,struct request *,int ,rq_end_io_fn *);extern void blk_unplug (struct request_queue *q); +extern void blk_queue_set_noflush (struct block_device *bdev);static inline struct request_queue *bdev_get_queue (struct block_device *bdev) {
include/linux/buffer_head.h +0 -2
@@ -33,7 +33,6 @@ enum bh_state_bits { BH_Boundary,/* Block is followed by a discontiguity */ BH_Write_EIO,/* I/O error on write */ BH_Ordered,/* ordered write */ - BH_Eopnotsupp,/* operation not supported (barrier) */ BH_Unwritten,/* Buffer is allocated on disk but not written */ BH_Quiet, /* Buffer Error Prinks to be quiet */
@@ -126,7 +125,6 @@ BUFFER_FNS(Delay, delay) BUFFER_FNS(Boundary, boundary) BUFFER_FNS(Write_EIO, write_io_error) BUFFER_FNS(Ordered, ordered) -BUFFER_FNS(Eopnotsupp, eopnotsupp) BUFFER_FNS(Unwritten, unwritten)#define bh_offset (bh) ((unsigned long)(bh)->b_data & ~PAGE_MASK)
Signature · 1 line
Jens Axboe
Re: [PATCH 1/7] block: Add block_flush_device()
Quoted 13 lines · Jens Axboe
Quoted 11 lines · Jens Axboe
Quoted 5 lines · Linus Torvalds
Quoted 2 lines · Ric Wheeler
The question is really what we do when you have a storage device in your box with a volatile write cache that does support flush or fua or similar.
Ok. Then you are talking about a different case - not EOPNOTSUPP.
So here's a test patch that attempts to just ignore such a failure to flush the caches. It will still flag the bio as
BIO_EOPNOTSUPP, but that's merely maintaining the information in case the caller does want to see if that barrier failed or not. It may not actually be useful, in which case we can just kill that flag.
Quoted 4 lines
Updated version, the previous missed most of the
buffer_eopnotsupp()checking. So this one also gets rid of the file system retry logic. Thanks to gfs2 Steve for pointing out that I missed gfs2, made me realize that I missed a lot more as well.
Wouldn't it be cleaner to simply finish with success status from blk_do_ordered()? That is the single place that all flush/barrier ops go through and semantically better place too.
Thanks.
Signature · 1 line
tejun
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Jens AxboeQuoted 3 lines · Jens Axboe
So here's a test patch that attempts to just ignore such a failure to flush the caches.
I suspect you should not do it like this.
Quoted 10 lines
fs/bio.c +1
-1@@ -1380,7 +1380,17 @@ void bio_check_pages_dirty(struct bio *bio)**/ void bio_endio (struct bio *bio,int error) { -if (error) +/*
fs/bio.c void bio_check_pages_dirty(struct bio *bio) · line 1393
Quoted 10 lines
fs/bio.c +10
-0+* Special case here - hide the -EOPNOTSUPP from the driver or +* block layer, dump a warning the first time this happens so that +* the admin knows that we may not provide the ordering guarantees +* that are needed. Don't clear the uptodate bit. +*/ +if (error == -EOPNOTSUPP &&bio_barrier (bio)) { +set_bit (BIO_EOPNOTSUPP , &bio->bi_flags); +blk_queue_set_noflush (bio->bi_bdev); + error =0 ; + }else if (error)
I suspect this part is just wrong.
I could easily imagine a driver that returns EOPNOTSUPP only for a certain _kind_ of bio.
For example, if the drive doesn't support FUA, then you cannot do a serialized IO operation, but you can still mostly do a serialized op without any IO attached to it.
IOW, the "empty flush" really _is_ special. An this check should not be in the generic "bio_endio()" case, it should only be in the special blkdev_issue_flush() case.
I think. No?
Linus
Re: [PATCH 1/7] block: Add block_flush_device()
Quoted 32 lines · Linus Torvalds
Quoted 3 lines · Jens Axboe
So here's a test patch that attempts to just ignore such a failure to flush the caches.
I suspect you should not do it like this.
Quoted 10 lines
fs/bio.c +1
-1@@ -1380,7 +1380,17 @@ void bio_check_pages_dirty(struct bio *bio)**/ void bio_endio (struct bio *bio,int error) { -if (error) +/* fs/bio.c void bio_check_pages_dirty(struct bio *bio) · line 1393
Quoted 10 lines
fs/bio.c +10
-0+* Special case here - hide the -EOPNOTSUPP from the driver or +* block layer, dump a warning the first time this happens so that +* the admin knows that we may not provide the ordering guarantees +* that are needed. Don't clear the uptodate bit. +*/ +if (error == -EOPNOTSUPP &&bio_barrier (bio)) { +set_bit (BIO_EOPNOTSUPP , &bio->bi_flags); +blk_queue_set_noflush (bio->bi_bdev); + error =0 ; + }else if (error)I suspect this part is just wrong.
Quoted 6 lines
I could easily imagine a driver that returns EOPNOTSUPP only for a certain _kind_ of bio.
For example, if the drive doesn't support FUA, then you cannot do a serialized IO operation, but you can still mostly do a serialized op without any IO attached to it.
FUA we should be able to reliably detect, it's really the cache flush operation itself that has caused headaches in the past. The -EOPNOTSUPP really comes from the block layer, not from the device driver. That's mainly due to the fact that we only send down the actual barrier, if the driver already said it supported them. If they do fail them, we probably need to pick up the -EIO bits and pieces and pretend it didn't happen as well. So it definitely needs more looking into, auditing, and testing. I'll do that tomorrow.
Quoted 5 lines
IOW, the "empty flush" really _is_ special. An this check should not be in the generic "
bio_endio()" case, it should only be in the specialblkdev_issue_flush()case.I think. No?
The empty flush is special and it is easy to fix that by itself. That should probably be the first patch in the series. But the retry logic and such for actual write barriers are the majority of the problems involved with supporting barriers, and those I want to get rid of.
I think it'll be more clear when I post a real patch series with the individual steps outlined.
Signature · 1 line
Jens Axboe
Re: [PATCH 1/7] block: Add block_flush_device()
Hello,
Quoted 4 lines · Jens Axboe
Quoted 3 lines
For example, if the drive doesn't support FUA, then you cannot do a serialized IO operation, but you can still mostly do a serialized op without any IO attached to it.
Quoted 8 lines
FUA we should be able to reliably detect, it's really the cache flush operation itself that has caused headaches in the past. The
-EOPNOTSUPPreally comes from the block layer, not from the device driver. That's mainly due to the fact that we only send down the actual barrier, if the driver already said it supported them. If they do fail them, we probably need to pick up the-EIObits and pieces and pretend it didn't happen as well. So it definitely needs more looking into, auditing, and testing. I'll do that tomorrow.
Yeah, we need to implement some kind of fallback logic such that filesystems get errors iff the underlying device actually failed to flush. For the most part, this shouldn't be too difficult.
There is a corner case for tag ordered requests in that retrying might end up putting the barrier on the platter after writes following it. Well, the problem isn't specific to fallback tho. The root problem is that later command get issued before the previous ones are finished and SCSI ordered tag doesn't mandate failure of earlier request to abort all the following ones, so by the time block layer knows about the failure, writes after the barrier might already be on the platter. I guess we'll have to ignore that for the time being.
Thanks.
Signature · 1 line
tejun
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Linus TorvaldsQuoted 16 lines · Linus Torvalds
Quoted 2 lines · Ric Wheeler
The question is really what we do when you have a storage device in your box with a volatile write cache that does support flush or fua or similar.
Ok. Then you are talking about a different case - not EOPNOTSUPP.
[ Although it may be related in that maybe the admin can _force_ a
EOPNOTSUPP thing for when he wants to disable any "write barrier implies flush" thing.IOW, we may end up with an _implementation_ detail where we overload a potential
QUEUE_FLUSH_EOPNOTSUPPflag with two meanings - either "the driver told me a barrier isn't supported" or "the admin set that same flag by hand to disable barrier-related flush commands".
Quoted 6 lines
But that's just an implementation detail, of course. We could use two different flags, we could do the flags at different levels, whatever. ]
Quoted 1 line
Using barriers & ordered transactions for these types of devices will give you a more reliable file system - less fsck time needed and better data integrity support for the (few?) applications that use fsync properly.
Sure. And it still shouldn't be the filesystem that _requires_ use of it.
That sounds reasonable enough. The key thing is how to squeeze as much reliability as possible out of what ever you have at the time.
Quoted 4 lines
The user (or low-level driver) may simply know better. The user may know that he trusts the disk more than anything else, and prefers to not actually emit the "FLUSH" command. Again, that's not something that the filesystem should know about, or care about. If the user trusts the disk subsystem and wants the performance, it's the users choice.
Even the _driver_ may know better.
True - high end arrays (as you mention below) will probably ack a flush request without flushing data, basically turning them into noops.
Quoted 3 lines
Knowing the kinds of firmware bugs those drives have, it could even be a driver that simply black-lists certain disks as having known-broken FLUSH commands. We have _CPU's_ that corrupt memory on cache writeback ("wbinvl"), and those things are a lot more tested than most driver firmware is.
Do you realize just how buggy some of those flash drives are? Some of them will literally (a) report the wrong size and (b) lock up if you try to read from the last sector. Oops. Do you really expect such crap to even bother to honor some flush command? Good luck with that. They're designed as a floppy replacement.
Sure - really cheap & crappy storage is easy enough to find. Definitely I agree that flush barriers would be wasted on them.
Quoted 2 lines
Now, you can tell me that I shouldn't put a reliable filesystem on an el-cheapo flash drive and expect it to work, but I'm sorry, you're wrong. People _are_ supposed to be able to move their data around, and the filesystem shouldn't make judgement calls. If you want judgement calls, call your mom. Not your filesystem.
File systems should try to do their best job with what they have, but we might also want to use a non-transaction based file system (ext2? ext4 w/o the journal like google?). Again, as you suggest, users (or distro installers?) can make that kind of choice.
Quoted 3 lines
For another example, the driver might be a driver for a high-end battery-backup SCSI RAID controller. It knows that the controller _will_ write things out in the right order even in the case of a crash, but it may also know that the controller _also_ has a way to force a flush to actual hardware.
When do you want to force a flush? For hotplug events, for example. Maybe the disks won't be _connected_ any more afterwards - then the battery backup on the controller won't be helping, will it? So there may well be a flush event thing, but it's really up to the admin to decide whether it should be connected to a write barrier thing, or be a separate admin activity.
For non-volatile write caches like these, you don't need to "flush" the storage write cache, you just need to move the data to the storage in the correct order.
As far as I know, non of this kind of information is exposed to higher levels in a standard way, so what people do today is to disable barriers (or assume, correctly as far as I know, that arrays will drop the flush requests :-))
Quoted 10 lines
Maybe the admin is extra careful and anal, and decides that he wants to flush to disk platters _despite_ the battery backup. Maybe he doesn't trust the card. Maybe he does. Whatever. The point is that the admin might want to set a driver flag that does the flush or not, adn it's totally not a filesystem issue.
See? The filesystem has absolutely _no_place_ deciding these kinds of things. The only thing it can ask for is "please serialize", but what _level_ of serialization is simply not a filesystem decision to make.
And that very much includes the level of serialization that says "no serialization what-so-ever, and please go absolutely crazy with your cache". Not your choice.
So no, you can't have a pony.
Linus
No room for a pony in my yard in any case :-)
ric
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Ric WheelerRic Wheeler wrote:
..
Quoted 1 line
As Mark pointed out, most S-ATA/SAS drives will flush the write cache when they see a bus reset so even without barriers, the cache will be preserved (or flushed) after a reboot or panic. Power outages are the problem barriers/flushes are meant to help with.
..
I still see barriers as a separate issue from flushes. Flushes are there for power failures and hot-removable devices.
Barriers are there for that, but also for better odds of data integrity in the even of a filesystem or kernel crash.
Even if I don't want the kernel needlessly flushing my battery-backed write caches, I still do want the barrier ordering that improves the odds of filesystem consistency in the event of a kernel crash.
Cheers
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Linus TorvaldsQuoted 2 lines · Linus Torvalds
Ok? Until you can see the bigger picture, just don't bother.
And this is really what it boils down to. Abstraction. Bigger picture. And the fact that the filesystem should DAMN WELL NOT THINK IT KNOWS WHAT IS GOING ON!
This is also fundamentally why returning that particular error is pointless. If the driver returns EOPNOTSUPP, there is simply never _any_ possible reason for upper layers to ever be informed about it - because there is not _any_ possible situation where they can do anything about it.
Even _thinking_ that they can do something about it is fundamentally flawed. It misses the entire point of having layering and abstraction and having a "block layer" there to do these kinds of things.
If you want to write your filesystem so that it interacts with the low-level device directly, go and write an MTD filesystem instead. Don't even _claim_ to care about generic filesystems like 'ext3' or something like that.
But if you try to be a "real" filesystem (ie general-purpose, meant to work on any random block device), don't come and whine about it when the block device then doesn't really do anything but read or write, or when the driver literally doesn't even _know_ how to serialize something because it doesn't even make sense in its world-view.
Don't mix up block layer and low-level driver issues with filesystem issues. The filesystem should say "block layer: flush the pending writes". And the block layer should try its best, but if the low-level driver says "that operation doesn't make sense for me", the block layer should just say "ok, whatever".
And the filesystem shouldn't know, and it most definitely mustr not act any differently. Because that's behind the abstraction, and there's no sane way to bring it _out_ of the abstraction that isn't fundamentally flawed (like thinking that it's always a SATA-II drive).
Linus
Re: [PATCH 1/7] block: Add block_flush_device()
Quoted 4 lines
And the filesystem shouldn't know, and it most definitely mustr not act any differently. Because that's behind the abstraction, and there's no sane way to bring it _out_ of the abstraction that isn't fundamentally flawed (like thinking that it's always a SATA-II drive).
How the file system responds has to depend upon what the users intents are with regards to still having their data.
In a lot of cases "flush if you can" makes good sense. In higher integrity cases you want a way to tell the device "flush if you can, do whatever else is needed to fake a flush if not" and in some cases you genuinely want to propogate errors back at mount time to say "sorry can't do this"
Agreed entirely that this shouldn't be expressed down the stack in terms of things like 'tags' or 'write with fua', but unless the different versions of it can be expressed, or refused you can't build a good enough abstraction. Throw and pray the block layer can fake it simply isn't a valid model for serious enterprise computing, and if people understood the worst cases, for a lot of non enterprise computing.
The second problem is who has sufficient information to efficiently handle decisions around ordering/barriers/flushes/single outstanding command and other strategies. I am skeptical that in the case where the underlying block subsystem provides suboptimal ordering/barrier facilities that it falling back to alternatives without letting the fs also change strategies will be efficient.
Alan
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Linus TorvaldsQuoted 7 lines · Linus Torvalds
Quoted 4 lines · Jens Axboe
Quoted 3 lines
It has _nothing_ to do with 'reckless'. It has everything to do with 'you can't do anything about it'.
Quoted 6 lines
Quoted 1 line
No, but you better damn well inform of such a discovery!
Well, if that's the issue, then just add a printk to that '
blkdev_issue_flush()', and now you have that informational message in _one_ place, instead of havign each filesystem having to do it over and over again.
Right, that's exactly what I want :-)
Quoted 30 lines
Quoted 5 lines
Quoted 2 lines
No. Returning an error just means that now the box is useless. Nobody can do anything about it. Not the admin, not the driver writer, not anybody.
What, that's nonsense. The admin can certainly check whether it's an issue or not, and he should.
If it's just informational, then again - why should the filesystem care?
Returning an error to the caller is never the right thing to do. The caller can't do anything sane about it.
If you argue that the admin wants to know, then sure, make that
if (
bio_flagged(bio, BIO_EOPNOTSUPP))
- ret =-EOPNOTSUPP;
+set_queue_noflush(q);"
set_queue_noflush()" function print a warning message when it sets the bit.Problem solved.
Quoted 3 lines
That's different from handling it in the kernel or in the application, but you have to inform about it. I honestly cannot fathom why you don't think that is important.
I cannot fathom why you can _possibly_ think that this is something that can and must be done something about in the caller. When the caller obviously has no real option except to ignore the error _anyway_.
Quoted 6 lines
That was always my point. Returning an error is INSANE, because ther is no valid thing that the caller can possibly do.
If you want it logged, fine. But THAT DOES NOT CHANGE ANYTHING. It would still be wrong to return the error, since the caller _still_ can't do anything about it.
I don't want to return -EOPNOTSUPP, I think this thread has become increasingly confusing. And it's probably largely due to me mixing write barriers into it, if we stick purely to blkdev_issue_flush(), then logging a warning and returning 0 is perfectly fine with me. My objection was to ignoring the "I can't flush" error in the first place, not returning 0.
Signature · 1 line
Jens Axboe
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Jens AxboeQuoted 10 lines · Jens Axboe
Quoted 9 lines · Linus Torvalds
Quoted 3 lines · Jens Axboe
Sorry, I just don't see much point to doing it this way instead. So now the fs will have to check a queue bit after it has issued the flush, how is that any better than having the 'error' returned directly?
No.
Now the fs SHOULD NEVER CHECK AT ALL.
Quoted 8 lines
Quoted 3 lines
Either it did the ordering, or the FS cannot do anything about it.
That's the point. EOPNOTSUPP is n ot a useful error message. You can't _do_ anything about it.
My point is that some file systems may or may not have different paths or optimizations depending on whether barriers are enabled and working or not. Apparently that's just reiserfs and Chris says we can remove it, so it is probably a moot point.
..
XFS appears to have something along those lines. I believe it tries to disable the drive write caches if it discovers that it cannot do cache flushes.
I'll check next time my MythTV box boots up.
It has a RAID0 under XFS, and the md raid0 code doesn't appear to pass the cache flushes to libata for raid0, so XFS complains and tries to turn off the write caches.
And I have a script to damn well turn them back ON again after it does so. Stupid thing tries to override user policy again.
Cheers
Re: [PATCH 1/7] block: Add block_flush_device()
Quoted 9 lines · Mark Lord
Quoted 4 lines · Jens Axboe
My point is that some file systems may or may not have different paths or optimizations depending on whether barriers are enabled and working or not. Apparently that's just reiserfs and Chris says we can remove it, so it is probably a moot point.
XFS appears to have something along those lines. I believe it tries to disable the drive write caches if it discovers that it cannot do cache flushes.
Perhaps; but speaking specifically about blkdev_issue_flush() --
nobody checks its return value at the present time.
Jeff
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Mark LordQuoted 20 lines · Mark Lord
Quoted 12 lines · Jens Axboe
Quoted 11 lines · Linus Torvalds
Quoted 3 lines · Jens Axboe
Sorry, I just don't see much point to doing it this way instead. So now the fs will have to check a queue bit after it has issued the flush, how is that any better than having the 'error' returned directly?
No.
Now the fs SHOULD NEVER CHECK AT ALL.
Either it did the ordering, or the FS cannot do anything about it.
Quoted 7 lines
Quoted 2 lines
That's the point. EOPNOTSUPP is n ot a useful error message. You can't _do_ anything about it.
My point is that some file systems may or may not have different paths or optimizations depending on whether barriers are enabled and working or not. Apparently that's just reiserfs and Chris says we can remove it, so it is probably a moot point.
Quoted 6 lines
..
XFS appears to have something along those lines. I believe it tries to disable the drive write caches if it discovers that it cannot do cache flushes.
If we get EOPNOTSUPP back from a submit_bh/submit_bio, the IO didn't happen. So, all the filesystems have code to try again without the barrier flag, and then stop doing barriers from then on.
I'm not saying this is a good or bad API, just explaining for this one example how it is being used today ;)
Quoted 9 lines
I'll check next time my MythTV box boots up.
It has a RAID0 under XFS, and the md raid0 code doesn't appear to pass the cache flushes to libata for raid0, so XFS complains and tries to turn off the write caches.And I have a script to damn well turn them back ON again after it does so. Stupid thing tries to override user policy again.
XFS does print a warning about not doing barriers any more, but the write cache should still be on. Especially with MD in front of it, the storage stack is pretty complex, a mounted filesystem would have a hard time knowing where to start to turn off write caches on each drive in the stack.
You can test this pretty easily:
dd if=/dev/zero of=foo bs=4k count=10000 oflag=direct
If that runs faster than 1MB/s the write cache is still on.
-chris
Re: [PATCH 1/7] block: Add block_flush_device()
Quoted 6 lines · Chris Mason
You can test this pretty easily:
dd if=/dev/zero of=foo bs=4k count=10000 oflag=direct
If that runs faster than 1MB/s the write cache is still on.
..
Or simply: hdparm -W /dev/sd? ## (for SATA/PATA drives)
Re: [PATCH 1/7] block: Add block_flush_device()
Quoted 10 lines · Mark Lord
Quoted 6 lines · Chris Mason
You can test this pretty easily:
dd if=/dev/zero of=foo bs=4k count=10000 oflag=direct
If that runs faster than 1MB/s the write cache is still on.
..
Or simply: hdparm -W
/dev/sd? ## (for SATA/PATA drives)
I'm afraid I tend to hammer on the drive instead of asking it politely, but I guess hdparm is trust worthy these days ;)
-chris
Re: [PATCH 1/7] block: Add block_flush_device()
In reply to Mark LordQuoted 18 lines · Mark Lord
Quoted 9 lines · Jens Axboe
Quoted 8 lines · Linus Torvalds
Quoted 3 lines · Jens Axboe
Sorry, I just don't see much point to doing it this way instead. So now the fs will have to check a queue bit after it has issued the flush, how is that any better than having the 'error' returned directly?
No.
Now the fs SHOULD NEVER CHECK AT ALL.
Quoted 8 lines
Quoted 4 lines
Either it did the ordering, or the FS cannot do anything about it.
That's the point. EOPNOTSUPP is n ot a useful error message. You can't _do_ anything about it.
My point is that some file systems may or may not have different paths or optimizations depending on whether barriers are enabled and working or not. Apparently that's just reiserfs and Chris says we can remove it, so it is probably a moot point.
Quoted 5 lines
..
XFS appears to have something along those lines. I believe it tries to disable the drive write caches if it discovers that it cannot do cache flushes.
No, it just stops issuing barriers if the initial mount-time test finds that they're not supported. ext3/4/reiserfs do similar.
Quoted 4 lines
I'll check next time my MythTV box boots up.
It has a RAID0 under XFS, and the md raid0 code doesn't appear to pass the cache flushes to libata for raid0, so XFS complains and tries to turn off the write caches.
doesn't touch write caches; just complains and stops issuing barriers.
Quoted 2 lines
And I have a script to damn well turn them back ON again after it does so. Stupid thing tries to override user policy again.
It does not do this.
-Eric
Re: [PATCH 1/7] block: Add block_flush_device()
Quoted 1 line · Eric Sandeen
Mark Lord wrote:
..
Quoted 6 lines
Quoted 3 lines
XFS appears to have something along those lines. I believe it tries to disable the drive write caches if it discovers that it cannot do cache flushes.
No, it just stops issuing barriers if the initial mount-time test finds that they're not supported. ext3/4/reiserfs do similar.
..
Okay. My apologies to the XFS folks!
I'll have to dig deeper to find out who/what is disabling the drive write caches, then.
Thanks
PATCH 2/7 ext3: call blkdev_issue_flush() on fsync()
In reply to Fernando Luis Vázquez CaoTo ensure that bits are truly on-disk after an fsync or fdatasync, we should force a disk flush explicitly when there is dirty data/metadata and the journal didn't emit a write barrier (either because metadata is not being synched or barriers are disabled).
---
fs/ext3/fsync.c +14 -5
@@ -45,6 +45,8 @@int ext3_sync_file (struct file * file,struct dentry *dentry,int datasync) {struct inode *inode = dentry->d_inode; +journal_t *journal =EXT3_SB (inode->i_sb)->s_journal; +unsigned long i_state = inode->i_state;int ret =0 ;J_ASSERT (ext3_journal_current_handle () ==NULL );
@@ -69,23 +71,30 @@ int ext3_sync_file(struct file * file, s*/ if (ext3_should_journal_data (inode)) { ret =ext3_force_commit (inode->i_sb); - goto out; +if (!ret && !(journal->j_flags &JFS_BARRIER )) + ret =block_flush_device (inode->i_sb->s_bdev); +return ret; } -if (datasync && !(inode->i_state &I_DIRTY_DATASYNC )) - goto out; +if (datasync && !(i_state &I_DIRTY_DATASYNC )) { +if (i_state &I_DIRTY_PAGES ) + ret =block_flush_device (inode->i_sb->s_bdev); +return ret; + }/* * The VFS has written the file data. If the inode is unaltered * then we need not start a commit. */ -if (inode->i_state & (I_DIRTY_SYNC |I_DIRTY_DATASYNC )) { +if (i_state & (I_DIRTY_SYNC |I_DIRTY_DATASYNC )) {struct writeback_control wbc = { .sync_mode =WB_SYNC_ALL , .nr_to_write =0 ,/* sys_fsync did this */ }; ret =sync_inode (inode, &wbc); +if (!ret && journal && !(journal->j_flags &JFS_BARRIER )) + ret =block_flush_device (inode->i_sb->s_bdev); } -out: +return ret; }
Re: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Quoted 4 lines · Fernando Luis Vázquez Cao
To ensure that bits are truly on-disk after an fsync or fdatasync, we should force a disk flush explicitly when there is dirty data/metadata and the journal didn't emit a write barrier (either because metadata is not being synched or barriers are disabled).
NACK.
As Eric commented on linux-ext4 (and I think it was Chris Mason deserves the credit for originally pointing this out), we don't need to call blkdev_issue_flush() after calling sync_inode(). That's because sync_inode() eventually (after going through a very deep call tree inside fs/fs-writeback.c) __sync_single_inode(), which calls write_inode(), which calls the filesystem-specific ->write_inode() function, which for both ext3 and ext4, ends up calling ext[34]_force_commit. Which, if barriers are enabled, will end up issuing a barrier after writing the commit block.
In the code paths that don't end up calling sync_inode() or ext4_force_commit(), (i.e., in the fdatasync() case) calling block_flush_device is appropriate. But as it stands, this patch (and the related one for ext4) will result in multiple unnecessary barrier requests being sent to the block layer.
So two out of the three places where this patch adds block_flush_device() are not necessary; as far as I can tell, only this one is one we should add.
fs/ext3/fsync.c int ext3_sync_file(struct file * file, s · line 83
Quoted 7 lines
fs/ext3/fsync.c +5
-2-if (datasync && !(inode->i_state &I_DIRTY_DATASYNC )) - goto out; +if (datasync && !(i_state &I_DIRTY_DATASYNC )) { +if (i_state &I_DIRTY_PAGES ) + ret =block_flush_device (inode->i_sb->s_bdev); +return ret; + }
A similar fixup is needed for the ext4 patch.
(And can we please start a new thread for these patches? Thanks!!)
Regards,
- Ted
Re: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Quoted 18 lines · Theodore Tso
Quoted 4 lines · Fernando Luis Vázquez Cao
To ensure that bits are truly on-disk after an fsync or fdatasync, we should force a disk flush explicitly when there is dirty data/metadata and the journal didn't emit a write barrier (either because metadata is not being synched or barriers are disabled).
NACK.
As Eric commented on linux-ext4 (and I think it was Chris Mason deserves the credit for originally pointing this out), we don't need to call
blkdev_issue_flush()after callingsync_inode(). That's becausesync_inode()eventually (after going through a very deep call tree insidefs/fs-writeback.c)__sync_single_inode(), which callswrite_inode(), which calls the filesystem-specific ->write_inode() function, which for both ext3 and ext4, ends up calling ext[34]_force_commit. Which, if barriers are enabled, will end up issuing a barrier after writing the commit block.
Quoted 6 lines
In the code paths that don't end up calling
sync_inode()orext4_force_commit(), (i.e., in thefdatasync()case) callingblock_flush_deviceis appropriate. But as it stands, this patch (and the related one for ext4) will result in multiple unnecessary barrier requests being sent to the block layer.
I'm not sure we want to stick Fernando with changing how barriers are done in individual filesystems, his patch is just changing the existing call points.
The ext34 code is especially tricky because there's no way to tell if a commit was actually done by sync_inode, so there's no way to know if an extra flush is really required.
I think we'll be better off if he keeps the existing logic and a different patch set is made for tuning the ext3 and ext4 code.
-chris
Theodore Tso
maintainerRe: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Quoted 4 lines · Chris Mason
I'm not sure we want to stick Fernando with changing how barriers are done in individual filesystems, his patch is just changing the existing call points.
Well, his patch actually added some calls to block_issue_flush(). But yes, it's probably better if he just changes the existing call points, and we can have the relevant filesystem maintainers double check to make sure that there aren't any new call points which are needed.
Quoted 3 lines
The ext34 code is especially tricky because there's no way to tell if a commit was actually done by
sync_inode, so there's no way to know if an extra flush is really required.
Yes, good point. What we need to do is to save inode->i_state *before* the call to sync_inode(), and issue the flush if the original value of (inode->i_state & I_DIRTY) == I_DIRTY_PAGES. But yeah, that's tricky.
Quoted 2 lines
I think we'll be better off if he keeps the existing logic and a different patch set is made for tuning the ext3 and ext4 code.
Agreed.
- Ted
Re: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Hello,
Quoted 9 lines · Theodore Tso
Quoted 3 lines · Chris Mason
I'm not sure we want to stick Fernando with changing how barriers are done in individual filesystems, his patch is just changing the existing call points.
Well, his patch actually added some calls to
block_issue_flush(). But yes, it's probably better if he just changes the existing call points, and we can have the relevant filesystem maintainers double check to make sure that there aren't any new call points which are needed.
How about having something like blk_ensure_cache_flushed() which issues flush iff there hasn't been any write since the last flush? It'll be easy to implement and will filter out duplicate flushes in most cases.
Thanks.
Signature · 1 line
tejun
Theodore Tso
maintainerRe: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Quoted 6 lines · Tejun Heo
How about having something like
blk_ensure_cache_flushed()which issues flush iff there hasn't been any write since the last flush? It'll be easy to implement and will filter out duplicate flushes in most cases.
I thought about such a thing, but my concern is that while this might suppress most unnecessary double flushes, some intervening write from another process might slip in which doesn't need to be flushed out. In other words "in most cases" means that "in some cases" we will take a performance hit thanks to the duplicate flushes. So this isn't something we should depend upon, although if we do detect back-to-back flushes, obviously we should filter them out.
So if we did something like this, it would be good if we had a debugging option which would detect double flushes, and printk a warning identifying where the call sites first and second flushes (by function name and line number), so that filesystem developers could detect the double flushes, and work to eliminate them.
Does that make sense?
- Ted
Re: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Hello,
Quoted 6 lines · Theodore Tso
Quoted 4 lines · Tejun Heo
How about having something like
blk_ensure_cache_flushed()which issues flush iff there hasn't been any write since the last flush? It'll be easy to implement and will filter out duplicate flushes in most cases.
Quoted 7 lines
I thought about such a thing, but my concern is that while this might suppress most unnecessary double flushes, some intervening write from another process might slip in which doesn't need to be flushed out. In other words "in most cases" means that "in some cases" we will take a performance hit thanks to the duplicate flushes. So this isn't something we should depend upon, although if we do detect back-to-back flushes, obviously we should filter them out.
Yeah, well, it all comes down to how most the "most" is. If all that's between the first flush and the second one are some code the cpu has to eat through, I don't think there's high chance of an IO going inbetween unless the IO was already there and gets scheduled inbetween (which can be avoided).
The thing is that detecting dup is possible but missing is not. If flush is missing in certain corner paths, nobody would know till somebody reviews the code. Even when the problem triggers, it would be rare and obscure enough to avoid proper diagnosis, so I think if the "most" is most enough, it could be the better way to do it. But, then again, I'm not a FS guy, so if such thing can be guaranteed in FSes without too much problem, no need to pull such a stunt at the block layer.
Quoted 7 lines
So if we did something like this, it would be good if we had a debugging option which would detect double flushes, and printk a warning identifying where the call sites first and second flushes (by function name and line number), so that filesystem developers could detect the double flushes, and work to eliminate them.
Does that make sense?
Yeap, that definitely sounds like a good idea. I'll put it on my todo list.
Thanks.
Signature · 1 line
tejun
Re: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
In reply to Tejun HeoQuoted 13 lines · Tejun Heo
Hello,
Quoted 9 lines · Theodore Tso
Quoted 3 lines · Chris Mason
I'm not sure we want to stick Fernando with changing how barriers are done in individual filesystems, his patch is just changing the existing call points.
Well, his patch actually added some calls to
block_issue_flush(). But yes, it's probably better if he just changes the existing call points, and we can have the relevant filesystem maintainers double check to make sure that there aren't any new call points which are needed.
Quoted 4 lines
How about having something like
blk_ensure_cache_flushed()which issues flush iff there hasn't been any write since the last flush? It'll be easy to implement and will filter out duplicate flushes in most cases.
My original ide implementation of flushes actually did this. My memory is a little hazy on why it was dropped, I'm guessing because it basically never triggered anyway.
Signature · 1 line
Jens Axboe
Re: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Quoted 12 lines · Jens Axboe
Quoted 11 lines · Tejun Heo
Hello,
Quoted 8 lines · Theodore Tso
Quoted 3 lines · Chris Mason
I'm not sure we want to stick Fernando with changing how barriers are done in individual filesystems, his patch is just changing the existing call points.
Well, his patch actually added some calls to
block_issue_flush(). But yes, it's probably better if he just changes the existing call points, and we can have the relevant filesystem maintainers double check to make sure that there aren't any new call points which are needed.
Quoted 8 lines
Quoted 4 lines
How about having something like
blk_ensure_cache_flushed()which issues flush iff there hasn't been any write since the last flush? It'll be easy to implement and will filter out duplicate flushes in most cases.My original ide implementation of flushes actually did this. My memory is a little hazy on why it was dropped, I'm guessing because it basically never triggered anyway.
Yeah, and it probably wouldn't trigger today unless we add new code that starts generating enough duplicate cache flushes for this to be significant...
And since duplicate cache flushes are harmless to the drive, you're only talking about no-op ATA command overhead. Which is only mildly notable on legacy IDE (eight or so inb/outb operations).
I would put duplicate cache flush filtering way, way down on the priority list, IMO.
Jeff
Re: [PATCH 2/7] ext3: call blkdev_issue_flush() on fsync()
Quoted 19 lines · Jeff Garzik
Quoted 18 lines · Jens Axboe
Quoted 16 lines · Tejun Heo
Hello,
Quoted 9 lines · Theodore Tso
Quoted 4 lines · Chris Mason
I'm not sure we want to stick Fernando with changing how barriers are done in individual filesystems, his patch is just changing the existing
call points.Well, his patch actually added some calls to
block_issue_flush(). But yes, it's probably better if he just changes the existing call points, and we can have the relevant filesystem maintainers double check to make sure that there aren't any new call points which are needed.How about having something like
blk_ensure_cache_flushed()which issues flush iff there hasn't been any write since the last flush? It'll be easy to implement and will filter out duplicate flushes in most cases.
Quoted 7 lines
Quoted 3 lines
My original ide implementation of flushes actually did this. My memory is a little hazy on why it was dropped, I'm guessing because it basically never triggered anyway.
Yeah, and it probably wouldn't trigger today unless we add new code that starts generating enough duplicate cache flushes for this to be significant...
Well, the thread was about adding such a call, so...
Quoted 6 lines
And since duplicate cache flushes are harmless to the drive, you're only talking about no-op ATA command overhead. Which is only mildly notable on legacy IDE (eight or so inb/outb operations).
I would put duplicate cache flush filtering way, way down on the priority list, IMO.
Yeap, unless FS guys need it, there's no reason to push it. Although having dup flush detection Theodore described (w/ callstack saving at issue time) would be nice for debugging.
Thanks.
Signature · 1 line
tejun
PATCH 3/7 ext4: call blkdev_issue_flush() on fsync()
In reply to Fernando Luis Vázquez CaoTo ensure that bits are truly on-disk after an fsync or fdatasync, we should force a disk flush explicitly when there is dirty data/metadata and the journal didn't emit a write barrier (either because metadata is not being synched or barriers are disabled).
---
fs/ext4/fsync.c +13 -7
@@ -48,6 +48,7 @@ int ext4_sync_file(struct file *file, st {struct inode *inode = dentry->d_inode;journal_t *journal =EXT4_SB (inode->i_sb)->s_journal; +unsigned long i_state = inode->i_state;int ret =0 ;J_ASSERT (ext4_journal_current_handle () ==NULL );
@@ -76,25 +77,30 @@ int ext4_sync_file(struct file *file, st*/ if (ext4_should_journal_data (inode)) { ret =ext4_force_commit (inode->i_sb); - goto out; +if (!ret && !(journal->j_flags &JBD2_BARRIER )) + ret =block_flush_device (inode->i_sb->s_bdev); +return ret; } -if (datasync && !(inode->i_state &I_DIRTY_DATASYNC )) - goto out; +if (datasync && !(i_state &I_DIRTY_DATASYNC )) { +if (i_state &I_DIRTY_PAGES ) + ret =block_flush_device (inode->i_sb->s_bdev); +return ret; + }/* * The VFS has written the file data. If the inode is unaltered * then we need not start a commit. */ -if (inode->i_state & (I_DIRTY_SYNC |I_DIRTY_DATASYNC )) { +if (i_state & (I_DIRTY_SYNC |I_DIRTY_DATASYNC )) {struct writeback_control wbc = { .sync_mode =WB_SYNC_ALL , .nr_to_write =0 ,/* sys_fsync did this */ }; ret =sync_inode (inode, &wbc); -if (journal && (journal->j_flags &JBD2_BARRIER )) -blkdev_issue_flush (inode->i_sb->s_bdev,NULL ); +if (!ret && journal && !(journal->j_flags &JBD2_BARRIER )) + ret =block_flush_device (inode->i_sb->s_bdev); } -out: +return ret; }
PATCH 4/7 vfs: call blkdev_issue_flush() from generic file_fsync() helper
In reply to Fernando Luis Vázquez CaoTo ensure that bits are truly on-disk after an fsync or fdatasync we should force a disk flush explicitly. This is necessary to have data integrity guarantees in filesystems such as FAT which do not provide their own fsync implementation and use the vfs helper instead.
---
fs/sync.c +5 -0
@@ -72,6 +72,11 @@ int file_fsync(struct file *filp, struct err =sync_blockdev (sb->s_bdev);if (!ret) ret = err; + + err =block_flush_device (sb->s_bdev); +if (!ret) + ret = err; +return ret; }
PATCH 5/7 vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
In reply to Fernando Luis Vázquez CaoAdd a sysfs knob to disable storage device writeback cache flushes.
---
block/blk-barrier.c +3 -0
@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;
block/blk-core.c +2 -1
@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) { err = -EOPNOTSUPP ; goto end_io; }
block/blk-sysfs.c +28 -0
@@ -151,6 +151,27 @@ static ssize_t queue_nonrot_store(structreturn ret; } +static ssize_t queue_wbcflush_show (struct request_queue *q,char *page) +{ +return queue_var_show (!blk_queue_nowbcflush (q), page); +} + +static ssize_t queue_wbcflush_store (struct request_queue *q,const char *page, +size_t count) +{ +unsigned long nm; +ssize_t ret =queue_var_store (&nm, page, count); + +spin_lock_irq (q->queue_lock); +if (nm) +queue_flag_clear (QUEUE_FLAG_NOWBCFLUSH , q); +else +queue_flag_set (QUEUE_FLAG_NOWBCFLUSH , q); +spin_unlock_irq (q->queue_lock); + +return ret; +} +static ssize_t queue_nomerges_show (struct request_queue *q,char *page) {return queue_var_show (blk_queue_nomerges (q), page);
@@ -258,6 +279,12 @@ static struct queue_sysfs_entry queue_no .store = queue_nonrot_store, }; +static struct queue_sysfs_entry queue_wbcflush_entry = { + .attr = {.name ="wbcflush" , .mode =S_IRUGO |S_IWUSR }, + .show = queue_wbcflush_show, + .store = queue_wbcflush_store, +}; +static struct queue_sysfs_entry queue_nomerges_entry = { .attr = {.name ="nomerges" , .mode =S_IRUGO |S_IWUSR }, .show = queue_nomerges_show,
@@ -284,6 +311,7 @@ static struct attribute *default_attrs[] &queue_iosched_entry.attr, &queue_hw_sector_size_entry.attr, &queue_nonrot_entry.attr, + &queue_wbcflush_entry.attr, &queue_nomerges_entry.attr, &queue_rq_affinity_entry.attr, &queue_iostats_entry.attr,
include/linux/blkdev.h +3 -0
@@ -452,6 +452,7 @@ struct request_queue#define QUEUE_FLAG_NONROT 14/* non-rotational device (SSD) */ #define QUEUE_FLAG_VIRT QUEUE_FLAG_NONROT/* paravirt device */ #define QUEUE_FLAG_IO_STAT 15/* do IO stats */ +#define QUEUE_FLAG_NOWBCFLUSH 16/* disable write-back cache flushing */ #define QUEUE_FLAG_DEFAULT ((1 << QUEUE_FLAG_IO_STAT) | \ (1 << QUEUE_FLAG_CLUSTER) | \
@@ -572,6 +573,8 @@ enum {#define blk_queue_stopped (q) test_bit(QUEUE_FLAG_STOPPED, &(q)->queue_flags)#define blk_queue_nomerges (q) test_bit(QUEUE_FLAG_NOMERGES, &(q)->queue_flags)#define blk_queue_nonrot (q) test_bit(QUEUE_FLAG_NONROT, &(q)->queue_flags) +#define blk_queue_nowbcflush (q) \ + test_bit(QUEUE_FLAG_NOWBCFLUSH, &(q)->queue_flags)#define blk_queue_io_stat (q) test_bit(QUEUE_FLAG_IO_STAT, &(q)->queue_flags)#define blk_queue_flushing (q) ((q)->ordseq)#define blk_queue_stackable (q) \
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 22 lines · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/block/blk-barrier.clinux-2.6.29/block/blk-barrier.cblock/blk-barrier.c +3
-0@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;diff -urNp
linux-2.6.29-orig/block/blk-core.clinux-2.6.29/block/blk-core.c
block/blk-core.c static inline void __generic_make_reques · line 1459
Quoted 9 lines
block/blk-core.c +2
-1@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) { err = -EOPNOTSUPP ; goto end_io; }
This (and the above hunk) should be changed. -EOPNOTSUPP means the target does not support barriers, that is a different thing to flushes not being needed. A file system issuing a barrier and getting -EOPNOTSUPP back will disable barriers, since it now thinks that ordering cannot be guaranteed.
A more appropriate change would be to successfully complete a flush without actually sending it down to the device if blk_queue_nowbcflush() is true. Then blkdev_issue_flush() would just work as well. It also needs to take stacking into account, or stacked drivers will have to propagate the settings up the stack. If you allow simply the barrier to be passed down, you get that for free.
block/blk-core.c
Quoted 6 lines
block/blk-core.c +6
-0+static struct queue_sysfs_entry queue_wbcflush_entry = { + .attr = {.name ="wbcflush" , .mode =S_IRUGO |S_IWUSR }, + .show = queue_wbcflush_show, + .store = queue_wbcflush_store, +}; +
Naming is also pretty bad, perhaps something like "honor_cache_flush" would be better, or perhaps "cache_flush_needed". At least something that is more descriptive of this setting actually controls, wbcflush does not do that.
Signature · 1 line
Jens Axboe
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 30 lines · Jens Axboe
Quoted 29 lines · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/block/blk-barrier.clinux-2.6.29/block/blk-barrier.cblock/blk-barrier.c +3
-0@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;diff -urNp
linux-2.6.29-orig/block/blk-core.clinux-2.6.29/block/blk-core.cblock/blk-core.c +2
-1@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) { err = -EOPNOTSUPP ;
Quoted 8 lines
block/blk-core.c static inline void __generic_make_reques · line 1459
Quoted 2 lines
block/blk-core.c +0
-0goto end_io; }This (and the above hunk) should be changed.
-EOPNOTSUPPmeans the target does not support barriers, that is a different thing to flushes not being needed. A file system issuing a barrier and getting-EOPNOTSUPPback will disable barriers, since it now thinks that ordering cannot be guaranteed.
The reason I decided to use -EOPNOTSUPP was that I wanted to keep barriers and device flushes from entering the block layer when they are not needed. I feared that if we pass them down the block stack (knowing in advance they will not be actually submitted to disk) we may end up slowing things down unnecessarily.
As you mentioned, filesystems such as ext3/4 will disable barriers if they get -EOPNOTSUPP when issuing one. I was planning to add a notifier mechanism so that we can notify filesystems has been a change in the barrier settings. This might be over-engineering, though. Especially considering that "-o remount,barrier=1" will bring us the barriers back.
Quoted 6 lines
A more appropriate change would be to successfully complete a flush without actually sending it down to the device if
blk_queue_nowbcflush()is true. Thenblkdev_issue_flush()would just work as well. It also needs to take stacking into account, or stacked drivers will have to propagate the settings up the stack. If you allow simply the barrier to be passed down, you get that for free.
Aren't we risking slowing things down? Does the small optimization above make sense (especially taking the remount trick into account)?
Maybe I am worrying too much about the possible performance penalty.
Quoted 11 lines
block/blk-core.c
Quoted 6 lines
block/blk-core.c +6
-0+static struct queue_sysfs_entry queue_wbcflush_entry = { + .attr = {.name ="wbcflush" , .mode =S_IRUGO |S_IWUSR }, + .show = queue_wbcflush_show, + .store = queue_wbcflush_store, +}; +Naming is also pretty bad, perhaps something like "
honor_cache_flush" would be better, or perhaps "cache_flush_needed". At least something that is more descriptive of this setting actually controls, wbcflush does not do that.
You are right, wbcflush is a pretty ugly name. I will use "honor_cache_flush" in the next iteration of the patches.
Thanks,
Fernando
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 40 lines · Fernando Luis Vázquez Cao
Quoted 30 lines · Jens Axboe
Quoted 29 lines · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/block/blk-barrier.clinux-2.6.29/block/blk-barrier.cblock/blk-barrier.c +3
-0@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;diff -urNp
linux-2.6.29-orig/block/blk-core.clinux-2.6.29/block/blk-core.cblock/blk-core.c +2
-1@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) { err = -EOPNOTSUPP ;Quoted 8 lines
block/blk-core.c static inline void __generic_make_reques · line 1459
Quoted 2 lines
block/blk-core.c +0
-0goto end_io; }This (and the above hunk) should be changed.
-EOPNOTSUPPmeans the target does not support barriers, that is a different thing to flushes not being needed. A file system issuing a barrier and getting-EOPNOTSUPPback will disable barriers, since it now thinks that ordering cannot be guaranteed.
Quoted 5 lines
The reason I decided to use
-EOPNOTSUPPwas that I wanted to keep barriers and device flushes from entering the block layer when they are not needed. I feared that if we pass them down the block stack (knowing in advance they will not be actually submitted to disk) we may end up slowing things down unnecessarily.
But that's just wrong, you need to make sure that the block layer / io scheduler doesn't reorder as well. It's a lot more complex than just the device end. So just returning -EOPNOTSUPP and pretending that you need not use barriers at the fs end is just wrong.
Quoted 6 lines
As you mentioned, filesystems such as ext3/4 will disable barriers if they get
-EOPNOTSUPPwhen issuing one. I was planning to add a notifier mechanism so that we can notify filesystems has been a change in the barrier settings. This might be over-engineering, though. Especially considering that "-o remount,barrier=1" will bring us the barriers back.
I think that is over-engineering.
Quoted 9 lines
Quoted 6 lines
A more appropriate change would be to successfully complete a flush without actually sending it down to the device if
blk_queue_nowbcflush()is true. Thenblkdev_issue_flush()would just work as well. It also needs to take stacking into account, or stacked drivers will have to propagate the settings up the stack. If you allow simply the barrier to be passed down, you get that for free.Aren't we risking slowing things down? Does the small optimization above make sense (especially taking the remount trick into account)?
It's not, I think you are missing the bigger picture.
Signature · 1 line
Jens Axboe
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 45 lines · Jens Axboe
Quoted 38 lines · Fernando Luis Vázquez Cao
Quoted 29 lines · Jens Axboe
Quoted 28 lines · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/block/blk-barrier.clinux-2.6.29/block/blk-barrier.cblock/blk-barrier.c +3
-0@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;diff -urNp
linux-2.6.29-orig/block/blk-core.clinux-2.6.29/block/blk-core.cblock/blk-core.c +2
-1@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) {Quoted 8 lines
block/blk-core.c static inline void __generic_make_reques · line 1459
Quoted 3 lines
block/blk-core.c +0
-0err = -EOPNOTSUPP ; goto end_io; }This (and the above hunk) should be changed.
-EOPNOTSUPPmeans the target does not support barriers, that is a different thing to flushes not being needed. A file system issuing a barrier and getting-EOPNOTSUPPback will disable barriers, since it now thinks that ordering cannot be guaranteed.Quoted 5 lines
The reason I decided to use
-EOPNOTSUPPwas that I wanted to keep barriers and device flushes from entering the block layer when they are not needed. I feared that if we pass them down the block stack (knowing in advance they will not be actually submitted to disk) we may end up slowing things down unnecessarily.
Quoted 4 lines
But that's just wrong, you need to make sure that the block layer / io scheduler doesn't reorder as well. It's a lot more complex than just the device end. So just returning
-EOPNOTSUPPand pretending that you need not use barriers at the fs end is just wrong.
I should have mentioned that in this patch set I was trying to tackle the blkdev_issue_flush() case only. As you pointed out, with the code above requests may get silently reordered across barriers inside the block layer.
The follow-up patch I am working on implements blkdev_issue_empty_barrier(), which should be used by filesystems that want to emit an empty barrier (as opposed to just triggering a device flush). Doing this we can optimize fsync() flushes (block_flush_device()) and filesystem-originated barriers (blkdev_issue_empty_barrier()) independently in the block layer.
I agree with you that the we should pass barriers down in __generic_make_request, but the optimization above for fsync()-originated blkdev_issue_flush()'s seems valid to me.
Does it make sense now?
Quoted 8 lines
Quoted 6 lines
As you mentioned, filesystems such as ext3/4 will disable barriers if they get
-EOPNOTSUPPwhen issuing one. I was planning to add a notifier mechanism so that we can notify filesystems has been a change in the barrier settings. This might be over-engineering, though. Especially considering that "-o remount,barrier=1" will bring us the barriers back.I think that is over-engineering.
Yep, we certainly agree on that point.
Quoted 10 lines
Quoted 8 lines
Quoted 6 lines
A more appropriate change would be to successfully complete a flush without actually sending it down to the device if
blk_queue_nowbcflush()is true. Thenblkdev_issue_flush()would just work as well. It also needs to take stacking into account, or stacked drivers will have to propagate the settings up the stack. If you allow simply the barrier to be passed down, you get that for free.Aren't we risking slowing things down? Does the small optimization above make sense (especially taking the remount trick into account)?
It's not, I think you are missing the bigger picture.
Sorry for not explaining myself properly. I will add a changelog and better documentation for the patches.
Thank you for your feedback!
- Fernando
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 55 lines · Fernando Luis Vázquez Cao
Quoted 45 lines · Jens Axboe
Quoted 38 lines · Fernando Luis Vázquez Cao
Quoted 29 lines · Jens Axboe
Quoted 28 lines · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/block/blk-barrier.clinux-2.6.29/block/blk-barrier.cblock/blk-barrier.c +3
-0@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;diff -urNp
linux-2.6.29-orig/block/blk-core.clinux-2.6.29/block/blk-core.cblock/blk-core.c +2
-1@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) {Quoted 8 lines
block/blk-core.c static inline void __generic_make_reques · line 1459
Quoted 3 lines
block/blk-core.c +0
-0err = -EOPNOTSUPP ; goto end_io; }This (and the above hunk) should be changed.
-EOPNOTSUPPmeans the target does not support barriers, that is a different thing to flushes not being needed. A file system issuing a barrier and getting-EOPNOTSUPPback will disable barriers, since it now thinks that ordering cannot be guaranteed.Quoted 5 lines
The reason I decided to use
-EOPNOTSUPPwas that I wanted to keep barriers and device flushes from entering the block layer when they are not needed. I feared that if we pass them down the block stack (knowing in advance they will not be actually submitted to disk) we may end up slowing things down unnecessarily.Quoted 4 lines
But that's just wrong, you need to make sure that the block layer / io scheduler doesn't reorder as well. It's a lot more complex than just the device end. So just returning
-EOPNOTSUPPand pretending that you need not use barriers at the fs end is just wrong.I should have mentioned that in this patch set I was trying to tackle the
blkdev_issue_flush()case only. As you pointed out, with the code above requests may get silently reordered across barriers inside the block layer.
Quoted 5 lines
The follow-up patch I am working on implements
blkdev_issue_empty_barrier(), which should be used by filesystems that want to emit an empty barrier (as opposed to just triggering a device flush). Doing this we can optimizefsync()flushes (block_flush_device()) and filesystem-originated barriers (blkdev_issue_empty_barrier()) independently in the block layer.
Not sure it makes sense to abstract that out into an api, it's basically just a bio_alloc(gfp, 0); with setting the bio fields and then submitting. Otherwise you'd have to either pass a ton of parameters, the caller will want to set end_io, bdev, etc anyway. And after that it's just submit_bio().
Quoted 3 lines
I agree with you that the we should pass barriers down in
__generic_make_request, but the optimization above for fsync()-originated blkdev_issue_flush()'s seems valid to me.
Of course, we need to do that. Anything else would be broken. The blkdev_issue_flush() should be changed to return 0, with the -EOPNOTSUPP being flag cached.
Signature · 1 line
Jens Axboe
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 60 lines · Jens Axboe
Quoted 53 lines · Fernando Luis Vázquez Cao
Quoted 44 lines · Jens Axboe
Quoted 38 lines · Fernando Luis Vázquez Cao
Quoted 29 lines · Jens Axboe
Quoted 28 lines · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/block/blk-barrier.clinux-2.6.29/block/blk-barrier.cblock/blk-barrier.c +3
-0@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;diff -urNp
linux-2.6.29-orig/block/blk-core.clinux-2.6.29/block/blk-core.cblock/blk-core.c +2
-1@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) {Quoted 8 lines
block/blk-core.c static inline void __generic_make_reques · line 1459
Quoted 3 lines
block/blk-core.c +0
-0err = -EOPNOTSUPP ; goto end_io; }This (and the above hunk) should be changed.
-EOPNOTSUPPmeans the target does not support barriers, that is a different thing to flushes not being needed. A file system issuing a barrier and getting-EOPNOTSUPPback will disable barriers, since it now thinks that ordering cannot be guaranteed.Quoted 5 lines
The reason I decided to use
-EOPNOTSUPPwas that I wanted to keep barriers and device flushes from entering the block layer when they are not needed. I feared that if we pass them down the block stack (knowing in advance they will not be actually submitted to disk) we may end up slowing things down unnecessarily.Quoted 4 lines
But that's just wrong, you need to make sure that the block layer / io scheduler doesn't reorder as well. It's a lot more complex than just the device end. So just returning
-EOPNOTSUPPand pretending that you need not use barriers at the fs end is just wrong.I should have mentioned that in this patch set I was trying to tackle the
blkdev_issue_flush()case only. As you pointed out, with the code above requests may get silently reordered across barriers inside the block layer.Quoted 5 lines
The follow-up patch I am working on implements
blkdev_issue_empty_barrier(), which should be used by filesystems that want to emit an empty barrier (as opposed to just triggering a device flush). Doing this we can optimizefsync()flushes (block_flush_device()) and filesystem-originated barriers (blkdev_issue_empty_barrier()) independently in the block layer.
Quoted 5 lines
Not sure it makes sense to abstract that out into an api, it's basically just a
bio_alloc(gfp, 0); with setting the bio fields and then submitting. Otherwise you'd have to either pass a ton of parameters, the caller will want to setend_io, bdev, etc anyway. And after that it's justsubmit_bio().
I will give it a try and see how it looks.
Quoted 7 lines
Quoted 3 lines
I agree with you that the we should pass barriers down in
__generic_make_request, but the optimization above for fsync()-originated blkdev_issue_flush()'s seems valid to me.Of course, we need to do that. Anything else would be broken. The
blkdev_issue_flush()should be changed to return 0, with the-EOPNOTSUPPbeing flag cached.
I am currently cooking a new iteration of these patches that do just that. I will be reposting in a new thread and keep you all CCed.
- Fernando
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
In reply to Fernando Luis Vázquez CaoQuoted 1 line · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
The horde of casual desktop users (with me included) would probably prefer having two settings -- one for filesystem barriers and one for fsync().
IOW I prefer higher performance at the cost of risking losing few last seconds/minutes of work in case of crash / powerfailure but I would still like to have the filesystem in the consistent state after such accident.
Thanks,
Bart
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 9 lines · Bartlomiej Zolnierkiewicz
Quoted 1 line · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
The horde of casual desktop users (with me included) would probably prefer having two settings -- one for filesystem barriers and one for
fsync().IOW I prefer higher performance at the cost of risking losing few last seconds/minutes of work in case of crash / powerfailure but I would still like to have the filesystem in the consistent state after such accident.
The knob is meant to control whether we really need to send a flush to the device or not, so it's an orthogonal issue to what you are talking about. For battery backed caches, we never need to flush. This knob is useful IFF we have devices with write back caches that STILL do a cache flush.
As such, I'd also prefer waiting with adding such a knob until such a device has actually be observed. No point in adding something just in case it may exist. And even then, it's probably even better handled in the driver.
Signature · 1 line
Jens Axboe
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 10 lines · Jens Axboe
Quoted 8 lines · Bartlomiej Zolnierkiewicz
Quoted 1 line · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
The horde of casual desktop users (with me included) would probably prefer having two settings -- one for filesystem barriers and one for
fsync().IOW I prefer higher performance at the cost of risking losing few last seconds/minutes of work in case of crash / powerfailure but I would still like to have the filesystem in the consistent state after such accident.
Quoted 5 lines
The knob is meant to control whether we really need to send a flush to the device or not, so it's an orthogonal issue to what you are talking about. For battery backed caches, we never need to flush. This knob is useful IFF we have devices with write back caches that STILL do a cache flush.
How do installers and/or kernels detect a battery-backed cache that does not need flush?
Jeff
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 11 lines · Jeff Garzik
Quoted 10 lines · Jens Axboe
Quoted 8 lines · Bartlomiej Zolnierkiewicz
Quoted 1 line · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
The horde of casual desktop users (with me included) would probably prefer having two settings -- one for filesystem barriers and one for
fsync().IOW I prefer higher performance at the cost of risking losing few last seconds/minutes of work in case of crash / powerfailure but I would still like to have the filesystem in the consistent state after such accident.
Quoted 8 lines
Quoted 5 lines
The knob is meant to control whether we really need to send a flush to the device or not, so it's an orthogonal issue to what you are talking about. For battery backed caches, we never need to flush. This knob is useful IFF we have devices with write back caches that STILL do a cache flush.
How do installers and/or kernels detect a battery-backed cache that does not need flush?
They obviously can't, otherwise it would not be an issue at all. And whether it's an issue is up for debate, until someone can point at such a device. You could add a white/blacklist.
So either that knob has to be turned by an administrator (yeah...), or the in-kernel info would have to be updated. Or a udev rule.
Signature · 1 line
Jens Axboe
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 16 lines · Jens Axboe
Quoted 15 lines · Jeff Garzik
Quoted 14 lines · Jens Axboe
Quoted 8 lines · Bartlomiej Zolnierkiewicz
Quoted 1 line · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
The horde of casual desktop users (with me included) would probably prefer having two settings -- one for filesystem barriers and one for
fsync().IOW I prefer higher performance at the cost of risking losing few last seconds/minutes of work in case of crash / powerfailure but I would still like to have the filesystem in the consistent state after such accident.
The knob is meant to control whether we really need to send a flush to the device or not, so it's an orthogonal issue to what you are talking about. For battery backed caches, we never need to flush. This knob is useful IFF we have devices with write back caches that STILL do a cache flush.
Quoted 6 lines
Quoted 2 lines
How do installers and/or kernels detect a battery-backed cache that does not need flush?
They obviously can't, otherwise it would not be an issue at all. And whether it's an issue is up for debate, until someone can point at such a device. You could add a white/blacklist.
Sorry, I guess I misinterpreted your dual "IFF" statement :)
I completely agree that the suggested knob, for disabling cache flush for these battery-backed devices, is at the present time addressing an entirely theoretical argument AFAICS.
Jeff
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 24 lines · Jeff Garzik
Quoted 16 lines · Jens Axboe
Quoted 15 lines · Jeff Garzik
Quoted 14 lines · Jens Axboe
Quoted 8 lines · Bartlomiej Zolnierkiewicz
Quoted 1 line · Fernando Luis Vázquez Cao
Add a sysfs knob to disable storage device writeback cache flushes.
The horde of casual desktop users (with me included) would probably prefer having two settings -- one for filesystem barriers and one for
fsync().IOW I prefer higher performance at the cost of risking losing few last seconds/minutes of work in case of crash / powerfailure but I would still like to have the filesystem in the consistent state after such accident.
The knob is meant to control whether we really need to send a flush to the device or not, so it's an orthogonal issue to what you are talking about. For battery backed caches, we never need to flush. This knob is useful IFF we have devices with write back caches that STILL do a cache flush.
Quoted 6 lines
Quoted 2 lines
How do installers and/or kernels detect a battery-backed cache that does not need flush?
They obviously can't, otherwise it would not be an issue at all. And whether it's an issue is up for debate, until someone can point at such a device. You could add a white/blacklist.
Quoted 5 lines
Sorry, I guess I misinterpreted your dual "IFF" statement :)
I completely agree that the suggested knob, for disabling cache flush for these battery-backed devices, is at the present time addressing an entirely theoretical argument AFAICS.
Guys, please look at the patch in the context of whole patchset posted not the current Linus' tree context only.
Patch #4 adds mandatory cache flush to fsync() (based on earlier Jeff's submission I guess) and patch #5 (this patch) adds a knob to disable cache flushing completely.
If patch #4 is going to be ever applied I want to have an option to disable mandatory cache flushing on fsync() -- I don't need it and I don't want it on my desktop (+ I somehow believe I'm not the only one). OTOH I do need it and I do want it on my server (+ to be on by default).
Actually legacy fsync() syscall is pretty bad interface in itself because:
a) it is synchronous
b) operates only on a single fd
and it encourages some pretty stupid (performance wise) usages like calling fsync() after every mail fetched. Adding mandatory cache flush to it only makes things worse (again looking from performance POV).
BTW in Linux world we never made any guarantees for fsync() on devices using write caching:
$ man fsync
...
If the underlying hard disk has write caching enabled, then the data
may not really be on permanent storage when fsync() / fdatasync()
return.
...aio_fsync() looks a bit better on a paper but no filesystem implements it currently...
Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
Quoted 5 lines · Bartlomiej Zolnierkiewicz
calling
fsync()after every mail fetched. Adding mandatory cache flush to it only makes things worse (again looking from performance POV).BTW in Linux world we never made any guarantees for
fsync()on devices using write caching:
Quite true, but I've always thought that was trading away correctness for performance... at a critical juncture where a consistency checkpoint was explicitly requested by the app.
My ideal would probably be blkdev cache flushing by default on fsync(2), with a block layer "desktop mode" knob to turn it off if you don't want it.
The current alternatives -- mount sync or disable blkdev writeback cache -- are far, far slower and punish the entire system just to provide a consistency checkpoint for a handful of fsync-needful apps.
Jeff
PATCH 6/7 xfs: propagate issue-flush error code
In reply to Fernando Luis Vázquez Caoblkdev_issue_flush() may fail (i.e. due to media error on FLUSH CACHE command execution) so its users should check for the return value.
(This issues was first spotted Bartlomiej Zolnierkiewicz)
---
fs/xfs/linux-2.6/xfs_buf.c +1 -0
@@ -1446,6 +1446,7 @@ xfs_free_buftarg( {xfs_flush_buftarg (btp,1 );if (mp->m_flags &XFS_MOUNT_BARRIER ) +/* FIXME: check return value */ xfs_blkdev_issue_flush (btp);xfs_free_bufhash (btp);iput (btp->bt_mapping->host);
fs/xfs/linux-2.6/xfs_super.c +2 -2
@@ -721,11 +721,11 @@ xfs_mountfs_check_barriers(xfs_mount_t * } } -void +int xfs_blkdev_issue_flush (xfs_buftarg_t *buftarg) { -blkdev_issue_flush (buftarg->bt_bdev,NULL ); +return block_flush_device (buftarg->bt_bdev); }STATIC void
fs/xfs/linux-2.6/xfs_super.h +1 -1
@@ -89,7 +89,7 @@ struct block_device;extern __uint64_t xfs_max_file_offset (unsigned int ); -extern void xfs_blkdev_issue_flush (struct xfs_buftarg *); +extern int xfs_blkdev_issue_flush (struct xfs_buftarg *);extern const struct export_operations xfs_export_operations;extern struct xattr_handler *xfs_xattr_handlers[];
fs/xfs/xfs_vnodeops.c +4 -4
@@ -678,20 +678,20 @@ xfs_fsync(xfs_iunlock (ip,XFS_ILOCK_EXCL ); } -if ((ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) { +if (!error && (ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) {/* * If the log write didn't issue an ordered tag we need * to flush the disk cache for the data device now. */ if (!log_flushed) -xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp); + error =xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp);/* * If this inode is on the RT dev we need to flush that * cache as well. */ -if (XFS_IS_REALTIME_INODE (ip)) -xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp); +if (!error &&XFS_IS_REALTIME_INODE (ip)) + error =xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp); }return error;
Re: [PATCH 6/7] xfs: propagate issue-flush error code
Quoted 55 lines · Fernando Luis Vázquez Cao
blkdev_issue_flush()may fail (i.e. due to media error on FLUSH CACHE command execution) so its users should check for the return value.(This issues was first spotted Bartlomiej Zolnierkiewicz)
Signed-off-by Bartlomiej Zolnierkiewicz <[email protected]>Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/fs/xfs/linux-2.6/xfs_buf.clinux-2.6.29/fs/xfs/linux-2.6/xfs_buf.cfs/xfs/linux-2.6/xfs_buf.c +1
-0@@ -1446,6 +1446,7 @@ xfs_free_buftarg( {xfs_flush_buftarg (btp,1 );if (mp->m_flags &XFS_MOUNT_BARRIER ) +/* FIXME: check return value */ xfs_blkdev_issue_flush (btp);xfs_free_bufhash (btp);iput (btp->bt_mapping->host);diff -urNp
linux-2.6.29-orig/fs/xfs/linux-2.6/xfs_super.clinux-2.6.29/fs/xfs/linux-2.6/xfs_super.cfs/xfs/linux-2.6/xfs_super.c +2
-2@@ -721,11 +721,11 @@ xfs_mountfs_check_barriers(xfs_mount_t * } } -void +int xfs_blkdev_issue_flush (xfs_buftarg_t *buftarg) { -blkdev_issue_flush (buftarg->bt_bdev,NULL ); +return block_flush_device (buftarg->bt_bdev); }STATIC voiddiff -urNp
linux-2.6.29-orig/fs/xfs/linux-2.6/xfs_super.hlinux-2.6.29/fs/xfs/linux-2.6/xfs_super.hfs/xfs/linux-2.6/xfs_super.h +1
-1@@ -89,7 +89,7 @@ struct block_device;extern __uint64_t xfs_max_file_offset (unsigned int ); -extern void xfs_blkdev_issue_flush (struct xfs_buftarg *); +extern int xfs_blkdev_issue_flush (struct xfs_buftarg *);extern const struct export_operations xfs_export_operations;extern struct xattr_handler *xfs_xattr_handlers[];diff -urNp
linux-2.6.29-orig/fs/xfs/xfs_vnodeops.clinux-2.6.29/fs/xfs/xfs_vnodeops.cfs/xfs/xfs_vnodeops.c +0
-0@@ -678,20 +678,20 @@ xfs_fsync(xfs_iunlock (ip,XFS_ILOCK_EXCL ); }
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 687
Quoted 10 lines
fs/xfs/xfs_vnodeops.c +2
-2-if ((ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) { +if (!error && (ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) {/* * If the log write didn't issue an ordered tag we need * to flush the disk cache for the data device now. */ if (!log_flushed) -xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp); + error =xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp);
This is different from my original patch which preserved the original error value...
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 694
Quoted 8 lines
fs/xfs/xfs_vnodeops.c +2
-2/* * If this inode is on the RT dev we need to flush that * cache as well. */ -if (XFS_IS_REALTIME_INODE (ip)) -xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp); +if (!error &&XFS_IS_REALTIME_INODE (ip)) + error =xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp);
This is also different and is a change in behavior (it makes sense IMHO but please document it).
Thanks,
Bart
Re: [PATCH 6/7] xfs: propagate issue-flush error code
In reply to Fernando Luis Vázquez CaoQuoted 7 lines · Fernando Luis Vázquez Cao
blkdev_issue_flush()may fail (i.e. due to media error on FLUSH CACHE command execution) so its users should check for the return value.(This issues was first spotted Bartlomiej Zolnierkiewicz)
Signed-off-by Bartlomiej Zolnierkiewicz <[email protected]>Signed-off-by Fernando Luis Vazquez Cao <[email protected]>
I think this patch is unnecessary as well as being broken.
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 681
Quoted 9 lines
diff -urNp
linux-2.6.29-orig/fs/xfs/xfs_vnodeops.clinux-2.6.29/fs/xfs/xfs_vnodeops.cfs/xfs/xfs_vnodeops.c +1
-1@@ -678,20 +678,20 @@ xfs_fsync(xfs_iunlock (ip,XFS_ILOCK_EXCL ); } -if ((ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) { +if (!error && (ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) {
That is wrong. Even if there was a error, we still need to flush the device if it hasn't already been done.
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 687
Quoted 7 lines
fs/xfs/xfs_vnodeops.c +1
-1/* * If the log write didn't issue an ordered tag we need * to flush the disk cache for the data device now. */ if (!log_flushed) -xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp); + error =xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp);
What happens if we get an EOPNOTSUPP here? That is a meaningless error to return to fsync()....
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 694
Quoted 8 lines
fs/xfs/xfs_vnodeops.c +2
-2/* * If this inode is on the RT dev we need to flush that * cache as well. */ -if (XFS_IS_REALTIME_INODE (ip)) -xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp); +if (!error &&XFS_IS_REALTIME_INODE (ip)) + error =xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp);
That is broken, too. The realtime device is a different device, so always should be flushed regardless of the return from the log device.
Cheers,
Dave.
Signature · 2 lines
Dave Chinner [email protected]
Re: [PATCH 6/7] xfs: propagate issue-flush error code
Quoted 19 lines · Dave Chinner
Quoted 7 lines · Fernando Luis Vázquez Cao
blkdev_issue_flush()may fail (i.e. due to media error on FLUSH CACHE command execution) so its users should check for the return value.(This issues was first spotted Bartlomiej Zolnierkiewicz)
Signed-off-by Bartlomiej Zolnierkiewicz <[email protected]>Signed-off-by Fernando Luis Vazquez Cao <[email protected]>I think this patch is unnecessary as well as being broken.
Quoted 7 lines
diff -urNp
linux-2.6.29-orig/fs/xfs/xfs_vnodeops.clinux-2.6.29/fs/xfs/xfs_vnodeops.cfs/xfs/xfs_vnodeops.c +0
-0@@ -678,20 +678,20 @@ xfs_fsync(xfs_iunlock (ip,XFS_ILOCK_EXCL ); }
Quoted 5 lines
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 681
Quoted 2 lines
fs/xfs/xfs_vnodeops.c +1
-1-if ((ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) { +if (!error && (ip->i_mount->m_flags &XFS_MOUNT_BARRIER ) && changed) {That is wrong. Even if there was a error, we still need to flush the device if it hasn't already been done.
If any of the previous writes failed there is no way to know what we are actually flushing. When we know things went awry I do not see the point in flushing the device since part of the data we were trying to sync might not have made it to the device.
Anyway this is a minor nitpick/policy issue that can be easily reverted to keep the previous behavior.
Quoted 10 lines
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 687
Quoted 7 lines
fs/xfs/xfs_vnodeops.c +1
-1/* * If the log write didn't issue an ordered tag we need * to flush the disk cache for the data device now. */ if (!log_flushed) -xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp); + error =xfs_blkdev_issue_flush (ip->i_mount->m_ddev_targp);What happens if we get an EOPNOTSUPP here? That is a meaningless error to return to
fsync()....
Please look at the code again. xfs_blkdev_issue_flush() calls blkdev_issue_flush() which turns EOPNOTSUPP into 0 to hide that error from filesystems. It is the non-EOPNOTSUPP errors that XFS should handle: the underlying device may support write cache flushes and still fail to flush (due to hardware errors)!
This patch is an attempt to fix the current situation.
Quoted 4 lines
Quoted 4 lines
fs/xfs/xfs_vnodeops.c +0
-0/* * If this inode is on the RT dev we need to flush that * cache as well. */
Quoted 8 lines
fs/xfs/xfs_vnodeops.c xfs_fsync( · line 694
Quoted 4 lines
fs/xfs/xfs_vnodeops.c +2
-2-if (XFS_IS_REALTIME_INODE (ip)) -xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp); +if (!error &&XFS_IS_REALTIME_INODE (ip)) + error =xfs_blkdev_issue_flush (ip->i_mount->m_rtdev_targp);That is broken, too. The realtime device is a different device, so always should be flushed regardless of the return from the log device.
Does it still make sense when writes to the log have failed?
Thanks!
- Fernando
PATCH 7/7 reiserfs: propagate issue-flush error code
In reply to Fernando Luis Vázquez Caoblkdev_issue_flush() may fail (i.e. due to media error on FLUSH CACHE command execution) so its users should check for the return value.
---
fs/reiserfs/file.c +3 -2
@@ -146,8 +146,9 @@ static int reiserfs_sync_file(struct filreiserfs_write_lock (p_s_inode->i_sb); barrier_done =reiserfs_commit_for_inode (p_s_inode);reiserfs_write_unlock (p_s_inode->i_sb); -if (barrier_done !=1 &&reiserfs_barrier_flush (p_s_inode->i_sb)) -blkdev_issue_flush (p_s_inode->i_sb->s_bdev,NULL ); +if (!n_err && barrier_done !=1 && +reiserfs_barrier_flush (p_s_inode->i_sb)) + n_err =block_flush_device (p_s_inode->i_sb->s_bdev);if (barrier_done <0 )return barrier_done;return (n_err <0 ) ? -EIO :0 ;
Re: [PATCH 7/7] reiserfs: propagate issue-flush error code
Quoted 11 lines · Fernando Luis Vázquez Cao
blkdev_issue_flush()may fail (i.e. due to media error on FLUSH CACHE command execution) so its users should check for the return value.Signed-off-by Bartlomiej Zolnierkiewicz <[email protected]>Signed-off-by Fernando Luis Vazquez Cao <[email protected]>---
diff -urNp
linux-2.6.29-orig/fs/reiserfs/file.clinux-2.6.29/fs/reiserfs/file.c
fs/reiserfs/file.c static int reiserfs_sync_file(struct fil · line 151
Quoted 8 lines
fs/reiserfs/file.c +3
-2@@ -146,8 +146,9 @@ static int reiserfs_sync_file(struct filreiserfs_write_lock (p_s_inode->i_sb); barrier_done =reiserfs_commit_for_inode (p_s_inode);reiserfs_write_unlock (p_s_inode->i_sb); -if (barrier_done !=1 &&reiserfs_barrier_flush (p_s_inode->i_sb)) -blkdev_issue_flush (p_s_inode->i_sb->s_bdev,NULL ); +if (!n_err && barrier_done !=1 && +reiserfs_barrier_flush (p_s_inode->i_sb)) + n_err =block_flush_device (p_s_inode->i_sb->s_bdev);
This is again different from my original patch
(the change in behavior should be documented).
Thanks,
Bart
PATCH 3/5 ext4: call blkdev_issue_flush on fsync
In reply to Fernando Luis Vázquez CaoTo ensure that bits are truly on-disk after an fsync or fdatasync, we should force a disk flush explicitly when there is dirty data/metadata and the journal didn't emit a write barrier (either because metadata is not being synched or barriers are disabled).
---
fs/ext4/fsync.c +13 -7
@@ -48,6 +48,7 @@ int ext4_sync_file(struct file *file, st {struct inode *inode = dentry->d_inode;journal_t *journal =EXT4_SB (inode->i_sb)->s_journal; +unsigned long i_state = inode->i_state;int ret =0 ;J_ASSERT (ext4_journal_current_handle () ==NULL );
@@ -76,25 +77,30 @@ int ext4_sync_file(struct file *file, st*/ if (ext4_should_journal_data (inode)) { ret =ext4_force_commit (inode->i_sb); - goto out; +if (!(journal->j_flags &JBD2_BARRIER )) +block_flush_device (inode->i_sb); +return ret; } -if (datasync && !(inode->i_state &I_DIRTY_DATASYNC )) - goto out; +if (datasync && !(i_state &I_DIRTY_DATASYNC )) { +if (i_state &I_DIRTY_PAGES ) +block_flush_device (inode->i_sb); +return ret; + }/* * The VFS has written the file data. If the inode is unaltered * then we need not start a commit. */ -if (inode->i_state & (I_DIRTY_SYNC |I_DIRTY_DATASYNC )) { +if (i_state & (I_DIRTY_SYNC |I_DIRTY_DATASYNC )) {struct writeback_control wbc = { .sync_mode =WB_SYNC_ALL , .nr_to_write =0 ,/* sys_fsync did this */ }; ret =sync_inode (inode, &wbc); -if (journal && (journal->j_flags &JBD2_BARRIER )) -blkdev_issue_flush (inode->i_sb->s_bdev,NULL ); +if (journal && !(journal->j_flags &JBD2_BARRIER )) +block_flush_device (inode->i_sb); } -out: +return ret; }
PATCH 4/5 vfs: call blkdev_issue_flush from generic file_fsync helper
In reply to Fernando Luis Vázquez CaoTo ensure that bits are truly on-disk after an fsync or fdatasync we should force a disk flush explicitly. This is necessary to have data integrity guarantees in filesystems such as FAT which do not provide their own fsync implementation and use the vfs helper instead.
---
fs/sync.c +5 -0
@@ -72,6 +72,11 @@ int file_fsync(struct file *filp, struct err =sync_blockdev (sb->s_bdev);if (!ret) ret = err; + + err =block_flush_device (sb); +if (!ret) + ret = err; +return ret; }
PATCH 5/5 vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes
In reply to Fernando Luis Vázquez CaoAdd a sysfs knob to disable storage device writeback cache flushes.
---
block/blk-barrier.c +3 -0
@@ -318,6 +318,9 @@ int blkdev_issue_flush(struct block_deviif (!q)return -ENXIO ; +if (blk_queue_nowbcflush (q)) +return -EOPNOTSUPP ; + bio =bio_alloc (GFP_KERNEL ,0 );if (!bio)return -ENOMEM ;
block/blk-core.c +2 -1
@@ -1452,7 +1452,8 @@ static inline void __generic_make_reques goto end_io; }if (bio_barrier (bio) &&bio_has_data (bio) && - (q->next_ordered ==QUEUE_ORDERED_NONE )) { + (blk_queue_nowbcflush (q) || + q->next_ordered ==QUEUE_ORDERED_NONE )) { err = -EOPNOTSUPP ; goto end_io; }
block/blk-sysfs.c +28 -0
@@ -151,6 +151,27 @@ static ssize_t queue_nonrot_store(structreturn ret; } +static ssize_t queue_wbcflush_show (struct request_queue *q,char *page) +{ +return queue_var_show (!blk_queue_nowbcflush (q), page); +} + +static ssize_t queue_wbcflush_store (struct request_queue *q,const char *page, +size_t count) +{ +unsigned long nm; +ssize_t ret =queue_var_store (&nm, page, count); + +spin_lock_irq (q->queue_lock); +if (nm) +queue_flag_clear (QUEUE_FLAG_NOWBCFLUSH , q); +else +queue_flag_set (QUEUE_FLAG_NOWBCFLUSH , q); +spin_unlock_irq (q->queue_lock); + +return ret; +} +static ssize_t queue_nomerges_show (struct request_queue *q,char *page) {return queue_var_show (blk_queue_nomerges (q), page);
@@ -258,6 +279,12 @@ static struct queue_sysfs_entry queue_no .store = queue_nonrot_store, }; +static struct queue_sysfs_entry queue_wbcflush_entry = { + .attr = {.name ="wbcflush" , .mode =S_IRUGO |S_IWUSR }, + .show = queue_wbcflush_show, + .store = queue_wbcflush_store, +}; +static struct queue_sysfs_entry queue_nomerges_entry = { .attr = {.name ="nomerges" , .mode =S_IRUGO |S_IWUSR }, .show = queue_nomerges_show,
@@ -284,6 +311,7 @@ static struct attribute *default_attrs[] &queue_iosched_entry.attr, &queue_hw_sector_size_entry.attr, &queue_nonrot_entry.attr, + &queue_wbcflush_entry.attr, &queue_nomerges_entry.attr, &queue_rq_affinity_entry.attr, &queue_iostats_entry.attr,
include/linux/blkdev.h +3 -0
@@ -452,6 +452,7 @@ struct request_queue#define QUEUE_FLAG_NONROT 14/* non-rotational device (SSD) */ #define QUEUE_FLAG_VIRT QUEUE_FLAG_NONROT/* paravirt device */ #define QUEUE_FLAG_IO_STAT 15/* do IO stats */ +#define QUEUE_FLAG_NOWBCFLUSH 16/* disable write-back cache flushing */ #define QUEUE_FLAG_DEFAULT ((1 << QUEUE_FLAG_IO_STAT) | \ (1 << QUEUE_FLAG_CLUSTER) | \
@@ -572,6 +573,8 @@ enum {#define blk_queue_stopped (q) test_bit(QUEUE_FLAG_STOPPED, &(q)->queue_flags)#define blk_queue_nomerges (q) test_bit(QUEUE_FLAG_NOMERGES, &(q)->queue_flags)#define blk_queue_nonrot (q) test_bit(QUEUE_FLAG_NONROT, &(q)->queue_flags) +#define blk_queue_nowbcflush (q) \ + test_bit(QUEUE_FLAG_NOWBCFLUSH, &(q)->queue_flags)#define blk_queue_io_stat (q) test_bit(QUEUE_FLAG_IO_STAT, &(q)->queue_flags)#define blk_queue_flushing (q) ((q)->ordseq)#define blk_queue_stackable (q) \
Quoted 1 line · Linus Torvalds
OS X, for example, doesn't do the disk barrier. It requires you to do a separate
FULL_FSYNC(or something similar) ioctl to get that. Apparently exactly because users don't expect quite _that_ big of a performance hit.
I can understand that, more from an admin standpoint than anything... ATA disks' FLUSH CACHE is horribly coarse-grained, all-or-nothing.
SCSI's SYNCHRONIZE CACHE at least gives us an optional (LBA, length) pair that can be used to avoid to flushing everything in the cache.
Microsoft has publicly proposed a WRITE BARRIER command for ATA, to try and improve the situation:
http://www.t13.org/Documents/UploadedDocuments/docs2007/e07174r0-Write_Barrier_Command_Proposal.doc
but that isn't in the field yet (if ever?)
Jeff
Quoted 9 lines · Linus Torvalds
Quoted 5 lines · Jeff Garzik
It is clearly possible to implement an fsync(2) that causes FLUSH CACHE to be issued, without adding full barrier support to a filesystem. It is likely doable to avoid touching per-filesystem code at all, if we issue the flush from a generic fsync(2) code path in the kernel.
Quoted 5 lines
We could easily do that. It would even work for most cases. The problematic ones are where filesystems do their own disk management, but I guess those people can do their own
fsync()management too.Somebody send me the patch, we can try it out.
Here's a simple patch that does that. Not even tested, it compiles. Note that file systems that currently do blkdev_issue_flush() in their ->sync() should then get it removed.
Quoted 10 lines
Quoted 1 line
Remember, fsync(2) means that the user _expects_ a performance hit.
Within reason, though.
OS X, for example, doesn't do the disk barrier. It requires you to do a separate
FULL_FSYNC(or something similar) ioctl to get that. Apparently exactly because users don't expect quite _that_ big of a performance hit.(Or maybe just because it was easier to do that way. Never attribute to malice what can be sufficiently explained by stupidity).
It'd be better to have a knob to control whether fsync() should care about the hardware side as well, instead of trying to teach applications to use FULL_FSYNC.
fs/sync.c +9 -0
@@ -8,6 +8,7 @@#include <linux/module.h> #include <linux/sched.h> #include <linux/writeback.h> +#include <linux/blkdev.h> #include <linux/syscalls.h> #include <linux/linkage.h> #include <linux/pagemap.h>
@@ -104,6 +105,7 @@ int vfs_fsync(struct file *file, struct dentry *dentry, int datasync) {const struct file_operations *fop;struct address_space *mapping; +struct block_device *bdev;int err, ret;/*
@@ -138,6 +140,13 @@ int vfs_fsync(struct file *file, struct dentry *dentry, int datasync) err =filemap_fdatawait (mapping);if (!ret) ret = err; + + bdev = mapping->host->i_sb->s_bdev; +if (bdev) { + err =blkdev_issue_flush (bdev,NULL ); +if (!ret) + ret = err; + } out:return ret; }
Signature · 1 line
Jens Axboe
Theodore Tso
maintainerQuoted 5 lines · Jens Axboe
Here's a simple patch that does that. Not even tested, it compiles. Note that file systems that currently do
blkdev_issue_flush()in their ->sync() should then get it removed.
That's going to be a mess. Ext3 implements an fsync() by requesting a journal commit, and then waiting for the commit to have taken place. The commit happens in another thread, kjournald. Knowing when it's OK not to do a blkdev_issue_flush() because the commit was triggered by an fsync() is going to be really messy. Could we at least have a flag in struct super which says, "We'll handle the flush correctly, please don't try to do it for us?"
- Ted
Quoted 7 lines · Theodore Tso
Quoted 5 lines · Jens Axboe
Here's a simple patch that does that. Not even tested, it compiles. Note that file systems that currently do
blkdev_issue_flush()in their ->sync() should then get it removed.
Quoted 7 lines
That's going to be a mess. Ext3 implements an
fsync()by requesting a journal commit, and then waiting for the commit to have taken place. The commit happens in another thread, kjournald. Knowing when it's OK not to do ablkdev_issue_flush()because the commit was triggered by anfsync()is going to be really messy. Could we at least have a flag in struct super which says, "We'll handle the flush correctly, please don't try to do it for us?"
Doing it in vfs_fsync also is completely wrong layering. If people want it for simple filesystems add it to file_fsync instead of messing up the generic helper. Removing well meaning but ill behaved policy from the generic path has been costing me far too much time lately.
And please add a tuneable for the flush. Preferable a generic one at the block device layer instead of the current mess where every filesystem has a slightly different option for barrier usage.
Quoted 18 lines · Christoph Hellwig
Quoted 7 lines · Theodore Tso
Quoted 5 lines · Jens Axboe
Here's a simple patch that does that. Not even tested, it compiles. Note that file systems that currently do
blkdev_issue_flush()in their ->sync() should then get it removed.Quoted 8 lines
That's going to be a mess. Ext3 implements an
fsync()by requesting a journal commit, and then waiting for the commit to have taken place. The commit happens in another thread, kjournald. Knowing when it's OK not to do ablkdev_issue_flush()because the commit was triggered by anfsync()is going to be really messy. Could we at least have a flag in struct super which says, "We'll handle the flush correctly, please don't try to do it for us?"
Quoted 9 lines
Doing it in
vfs_fsyncalso is completely wrong layering. If people want it for simple filesystems add it tofile_fsyncinstead of messing up the generic helper. Removing well meaning but ill behaved policy from the generic path has been costing me far too much time lately.And please add a tuneable for the flush. Preferable a generic one at the block device layer instead of the current mess where every filesystem has a slightly different option for barrier usage.
I agree that we need to be careful not to put extra device flushes if the file system handles this properly. They can be quite expensive (say 10-20ms on a busy s-ata disk).
I have also seen some SSD devices have performance that drops into the toilet when you start flushing their volatile caches.
ric
Quoted 3 lines · Christoph Hellwig
And please add a tuneable for the flush. Preferable a generic one at the block device layer instead of the current mess where every filesystem has a slightly different option for barrier usage.
At the very least, IMO the block layer should be able to notice when barriers need not be translated into cache flushes. Most notably when wb cache is disabled on the drive, something easy to auto-detect, but probably a manual switch also, for people with enterprise battery-backed storage and such.
Jeff
Quoted 10 lines · On Fri, 27 Mar 2009 16:38:35 -0400 Jeff Garzik <[email protected]> wrote:
Quoted 3 lines · Christoph Hellwig
And please add a tuneable for the flush. Preferable a generic one at the block device layer instead of the current mess where every filesystem has a slightly different option for barrier usage.
At the very least, IMO the block layer should be able to notice when barriers need not be translated into cache flushes. Most notably when wb cache is disabled on the drive, something easy to auto-detect, but probably a manual switch also, for people with enterprise battery-backed storage and such.
The storage drivers for those cases already generally know this and treat cache flush requests as "has hit nvram", even the non enterprise ones.
Quoted 5 lines · Jeff Garzik
At the very least, IMO the block layer should be able to notice when barriers need not be translated into cache flushes. Most notably when wb cache is disabled on the drive, something easy to auto-detect, but probably a manual switch also, for people with enterprise battery-backed storage and such.
Yeah, that's why I suggested to have the tuning knob in the block layer and not in the fses when this came up last time.
Quoted 14 lines · Jens Axboe
Quoted 13 lines · Linus Torvalds
Quoted 5 lines · Jeff Garzik
It is clearly possible to implement an fsync(2) that causes FLUSH CACHE to be issued, without adding full barrier support to a filesystem. It is likely doable to avoid touching per-filesystem code at all, if we issue the flush from a generic fsync(2) code path in the kernel.
We could easily do that. It would even work for most cases. The problematic ones are where filesystems do their own disk management, but I guess those people can do their own
fsync()management too.
Quoted 6 lines
Quoted 1 line
Somebody send me the patch, we can try it out.
Here's a simple patch that does that. Not even tested, it compiles. Note that file systems that currently do
blkdev_issue_flush()in their ->sync() should then get it removed.
The filesystems vary a bit, but in general the perfect fsync (in a mail server workload) works something like this:
step1: write out and wait for any dirty data
step2: join the running transaction
step3: hang around a bit and wait for friends and neighbors
step4: commit the transaction
step4a: write the log blocks
step4b: barrier. This barrier also makes sure the data is on disk
step4c: write the commit block
step4d: barrier. This barrier makes sure the commit block is on disk.
For ext34 and reiserfs, steps 4b,c,d are actually one call to submit_bh where two caches flushes are done for us, but they really are two cache flushes.
During step 3, we collect a bunch of other procs who are hopefully also running fsync. If we collect 50 procs, then single the barrier in step 5b does a cache flush on the data writes of all 50. 50 flushes this patch does would be one flush if the FS did it right.
In a multi-process fsync heavy workload, every extra barrier is going to have work to do because someone is always sending data down.
The flushes done by this patch also aren't helpful for the journaled filesystem. If we remove the barriers from step 4b or 4d, we no longer have a consistent FS on power failure. Log checksumming may allow us to get rid of the barrier in step 4b, but then we wouldn't know the data blocks were on disk before the transaction commit, and we've had a few discussions on that already over the last two weeks.
The patch also assumes the FS has one bdev, which isn't true for btrfs.
xfs and btrfs at least want more control over that filemap_fdatawrite/wait step because we have to repeat it inside the FS anyway to make sure the inode properly updated before the commit. I'd much rather see a dumb fsync helper that looks like Jens' vfs_fsync, and then let the filesystems make their own replacement for the helper in a new address space operation or super operation.
That way we could also run the fsync on directories without the directory mutex held, which is much faster.
Also, the patch is sending the return value from blkdev_issue_flush out through vfs_fsync, which means I think it'll send -EOPNOTSUPP out to userland.
So, I should be able to run any benchmark that does an fsync with this patch and find large regressions. It turns out it isn't quite that easy.
First, I found that ext4 has a neat feature where it is already doing an extra barrier on every fsync.
Even with that removed, the flushes made ext4 faster (doh!). Looking at the traces, ext4 and btrfs (which is totally unchanged by this patch) both do a good job of turning my simple fsync hammering programs into mostly sequential IO.
The extra flushes are just writing mostly sequential IO, and so they aren't really hurting overall tput. Plus, Ric reminded me the drive may have some pass through for larger sequential writes, and ext4 and btrfs may be doing enough to trigger that.
I should be able to run more complex benchmarks and get really bad numbers out of this patch with ext4, but instead I'll try ext3...
This is a simple run with fs_mark using 64 threads to create 20k files with fsync. I timed how long it took to create 900 files. Lower numbers are better.
unpatched patched
ext3 236s 286s
-chris
Jeff, if you drop my CC on reply, I wont see your messages for ages.
Quoted 17 lines · Jeff Garzik
Quoted 16 lines · Jens Axboe
Quoted 7 lines · Jeff Garzik
Stating "fsync already does that" borders on false, because that assumes
(a) the user has a fs that supports barriers
(b) the user is actually aware of a 'barriers' mount option and what it means
(c) the user has turned on an option normally defaulted to off.Or in other words, it pretty much never happens.
That is true, except if you use xfs/ext4. And this discussion is fine, as was the one a few months back that got ext4 to enable barriers by default. If I had submitted patches to do that back in 2001/2 when the barrier stuff was written, I would have been shot for introducing such a slow down. After people found out that it just wasn't something silly, then you have a way to enable it.
Quoted 6 lines
Quoted 3 lines
I'd still wager that most people would rather have a 'good enough fsync' on their desktops than incur the penalty of barriers or write through caching. I know I do.
That's a strawman argument: The choice is not between "good enough fsync" and full use of barriers / write-through caching, at all.
Then let me rephrase that to "most users don't care about full integrity fsync()". If it kills their firefox performance, most will wont to turn it off. Personally I'd never use it on my notebook or desktop box, simply because I don't care strongly enough. I'd rather fix things up in the very unlikely event of a crash WITH corruption.
Quoted 4 lines
It is clearly possible to implement an fsync(2) that causes FLUSH CACHE to be issued, without adding full barrier support to a filesystem. It is likely doable to avoid touching per-filesystem code at all, if we issue the flush from a generic fsync(2) code path in the kernel.
Of course, it would be trivial. Just add a blkdev_issue_flush() to vfs_fsync().
Quoted 8 lines
Thus, you have a "third way": fsync(2) gives the guarantee it is supposed to, but you do not take the full performance hit of barriers-all-the-time.
Remember, fsync(2) means that the user _expects_ a performance hit.
And they took the extra step to call fsync(2) because they want a guarantee, not a lie.
s/user/application.
Signature · 1 line
Jens Axboe
Quoted 6 lines · Jens Axboe
Another problem is that
FLUSH_CACHEsucks. Really. And not just on ext3/ordered, generally. Write a 50 byte file, fsync, flush cache and wit for the world to finish. Pretty hard to teach people to use a nicerfdatasync(), when the majority of the cost now becomes flushing the cache of that 1TB drive you happen to have 8 partitions on. Good luck with that.
(responding to an email way back near the start of the thread)
I emailed Microsoft about their proposal to add a WRITE BARRIER command to ATA, documented at
http://www.t13.org/Documents/UploadedDocuments/docs2007/e07174r0-Write_Barrier_Command_Proposal.doc
The MSFT engineer said they were definitely still pursuing this proposal.
IMO we could look at this too, or perhaps come up with an alternate proposal like FLUSH CACHE RANGE(s).
Jeff
Quoted 14 lines · Jeff Garzik
Quoted 6 lines · Jens Axboe
Another problem is that
FLUSH_CACHEsucks. Really. And not just on ext3/ordered, generally. Write a 50 byte file, fsync, flush cache and wit for the world to finish. Pretty hard to teach people to use a nicerfdatasync(), when the majority of the cost now becomes flushing the cache of that 1TB drive you happen to have 8 partitions on. Good luck with that.(responding to an email way back near the start of the thread)
I emailed Microsoft about their proposal to add a WRITE BARRIER command to ATA, documented at
http://www.t13.org/Documents/UploadedDocuments/docs2007/e07174r0-Write_Barrier_Command_Proposal.doc
Quoted 6 lines
The MSFT engineer said they were definitely still pursuing this proposal.
IMO we could look at this too, or perhaps come up with an alternate proposal like FLUSH CACHE RANGE(s).
Jeff
I agree that it is worth getting better mechanisms in place - the cache flush is really primitive. Now we just need a victim to sit in on T13/T10 standards meetings :-)
ric
Quoted 11 lines · Ric Wheeler
Quoted 10 lines · Jeff Garzik
Quoted 6 lines · Jens Axboe
Another problem is that
FLUSH_CACHEsucks. Really. And not just on ext3/ordered, generally. Write a 50 byte file, fsync, flush cache and wit for the world to finish. Pretty hard to teach people to use a nicerfdatasync(), when the majority of the cost now becomes flushing the cache of that 1TB drive you happen to have 8 partitions on. Good luck with that.(responding to an email way back near the start of the thread)
Quoted 8 lines
Quoted 6 lines
I emailed Microsoft about their proposal to add a WRITE BARRIER command to ATA, documented at
http://www.t13.org/Documents/UploadedDocuments/docs2007/e07174r0-Write_Barrier_Command_Proposal.docThe MSFT engineer said they were definitely still pursuing this proposal.
IMO we could look at this too, or perhaps come up with an alternate proposal like FLUSH CACHE RANGE(s).
I agree that it is worth getting better mechanisms in place - the cache flush is really primitive. Now we just need a victim to sit in on T13/T10 standards meetings :-)
Heck, we could even do a prototype implementation with the help of Mark Lord's sata_mv target mode support...
Jeff
Quoted 3 lines · Jeff Garzik
Quoted 2 lines · Ric Wheeler
Quoted 1 line · Jeff Garzik
Jens Axboe wrote:
..
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
IMO we could look at this too, or perhaps come up with an alternate proposal like FLUSH CACHE RANGE(s).
I agree that it is worth getting better mechanisms in place - the cache flush is really primitive. Now we just need a victim to sit in on T13/T10 standards meetings :-)
Heck, we could even do a prototype implementation with the help of Mark Lord's
sata_mvtarget mode support...
..
Speaking of which.. you probably won't see the preliminary rev of sata_mv + target_mode until sometime this weekend.
It's going to be something quite simple for 2.6.30, and we can expand on that in later kernels.
Cheers
Quoted 2 lines · Jeff Garzik
So, no, for 95% of Linux users, fsync does _not_ already do that. If you are lucky enough to use XFS or ext4, you're covered. That's it.
reiserfs also does the correct thing. As does ext3 on suse kernels.
Quoted 9 lines · Linus Torvalds
Quoted 4 lines · Theodore Tso
Try ext4, I think you'll like it. :-)
Failing that, data=writeback for single-user machines is probably your best bet.
Isn't that the same fix? ext4 just defaults to the crappy "writeback" behavior, which is insane.
Quoted 7 lines
Sure, it makes things _much_ smoother, since now the actual data is no longer in the critical path for any journal writes, but anybody who thinks that's a solution is just incompetent.
We might as well go back to ext2 then. If your data gets written out long after the metadata hit the disk, you are going to hit all kinds of bad issues if the machine ever goes down.
Not really...
Regardless of any journalling, a power-fail or a crash is almost certainly going to cause "data loss" of some variety. We simply didn't get to sync everything we needed to (otherwise we'd all be shutting down our computers with the SCRAM switches just for kicks). The difference is, with ext3/4 (in any journal mode) we guarantee our metadata is consistent. This means that we won't double-allocate or leak inodes or blocks, which means that we can safely *write* to the filesystem as soon as we replay the journal. With ext2 you *CAN'T* do that at all, as somebody may have allocated an inode but not yet marked it as in use. The only way to safely figure all that out without journalling is an fsck run.
That difference between ext4 and ext3-in-writeback-mode is this: If you get a crash in the narrow window *after* writing initial metadata and before writing the data, ext4 will give you a zero length file, whereas ext3-in-writeback-mode will give you a proper-length file filled with whatever used to be on disk (might be the contents of a previous /etc/shadow, or maybe somebody's finance files).
In that same situation, ext3 in data-ordered or data-journal mode will "close" the window by preventing anybody else from making forward progress until the data and the metadata are both updated. The thing is, even on ext3 I can get exactly the same kind of behavior with an appropriately timed "kill -STOP $dumb_program", followed by a power failure 60 seconds later. It's a relatively obvious race condition...
When you create a file, you can't guarantee that all of that file's data and metadata has hit disk until after an fsync() call returns. The only *possible* exceptions are in cases like the previously-mentioned (and now patched) open(A)+write(A)+close(A)+rename(A,B), where the rename-over-existing-file should act as an implicit filesystem barrier. It should ensure that all writes to the file get flushed before it is renamed on top of an existing file, simply because so much UNIX software expects it to act that way.
When you're dealing with programs that simply open()+ftruncate()+write()+close(), however... there's always going to be a window in-between the ftruncate and the write where the file *is* an empty file, and in that case no amount of operating-system-level cleverness can deal with application-level bugs.
Cheers,
Kyle Moffett
Quoted 3 lines · Kyle Moffett
Regardless of any journalling, a power-fail or a crash is almost certainly going to cause "data loss" of some variety.
The point is, if you write your metadata earlier (say, every 5 sec) and the real data later (say, every 30 sec), you're actually MORE LIKELY to see corrupt files than if you try to write them together.
And if you write your data _first_, you're never going to see corruption at all.
This is why I absolutely _detest_ the idiotic ext3 writeback behavior. It literally does everything the wrong way around - writing data later than the metadata that points to it. Whoever came up with that solution was a moron. No ifs, buts, or maybes about it.
Linus
Quoted 5 lines · Theodore Tso
However, what I've found, though, is that if you're just doing a local copy from one hard drive to another, or downloading a huge iso file from an ftp server over a wide area network, the
fsync()delays really don't get *that* bad, even with ext3. At least, I haven't found a workload that doesn't involve either dd if=/dev/zero or a massive
Quoted 8 lines
amount of data coming in over the network that will cause
fsync()delays in the > 1-2 second category. Ext3 has been around for a long time, and it's only been the last couple of years that people have really complained about this; my theory is that it was the rise of > 10 megabit ethernets and the use of systems like distcc that really made this problem really become visible. The only realistic workload I've found that triggers this requires a fast network dumping data to a local filesystem.
It's pretty easy to reproduce it these days. Here's my setup, and it's not even that fancy: Dual core Xeon, 8GB RAM, SATA RAID1 array, GigE network. All it takes is a single client writing a large file using Samba or NFS to introduce huge latencies.
Looking at the raw throughput, the server's disks can sustain 30-60MB/s writes (older disks), but the network can handle up to ~100MB/s. Throw in some other random seeky IO on the server, a bunch of fragmentation and it's sustained write throughput in reality for these writes is more like 10-25MB/s, far slower than the rate at which a client can throw data at it.
5% dirty_ratrio * 8GB is 400MB. Let's say in reality the system is flushing 20MB/s to disk, this is a delay of up to 20 seconds. Let's say you have a user application which needs to fsync a number of small files (and unfortunately they are done serially) and now I've got applications (like Firefox) which basically remain unresponsive the entire time the write is being done.
Quoted 4 lines
(I'm sure someone will be ingeniuous enough to find something else though, and if they're interested, I've attached an fsync latency tester to this note. If you find something; let me know, I'd be interested.)
Thanks - I'll give the program a shot later with my test case and see what it reports. My simple test case[1] for reproducing this has reported 6-45 seconds depending on the system. I'll try it with the previously mentioned workload as well.
-Dave
Quoted 10 lines · David Rees
Quoted 3 lines · Theodore Tso
The only realistic workload
I've found that triggers this requires a fast network dumping data to a local filesystem.It's pretty easy to reproduce it these days. Here's my setup, and it's not even that fancy: Dual core Xeon, 8GB RAM, SATA RAID1 array, GigE network. All it takes is a single client writing a large file using Samba or NFS to introduce huge latencies.
Quoted 11 lines
Looking at the raw throughput, the server's disks can sustain 30-60MB/s writes (older disks), but the network can handle up to ~100MB/s. Throw in some other random seeky IO on the server, a bunch of fragmentation and it's sustained write throughput in reality for these writes is more like 10-25MB/s, far slower than the rate at which a client can throw data at it.
Quoted 4 lines
(I'm sure someone will be ingeniuous enough to find something else though, and if they're interested, I've attached an fsync latency tester to this note. If you find something; let me know, I'd be interested.)
OK, two simple tests on this system produce latencies well over 1-2s using your fsync-tester.
The network client writing to disk scenario (~1GB file) resulted in this:
fsync time: 6.5272
fsync time: 35.6803
fsync time: 15.6488
fsync time: 0.3570
One thing to note - writing to this particular array seems to have higher than expected latency without the big write, on the order of 0.2 seconds or so. I think this is because the system is not idle and has a good number of programs on it doing logging and other small bits of IO. vmstat 5 shows the system writing out about 300-1000 under the bo column.
Copying that file to a separate disk was not as bad, but there were still some big spikes:
fsync time: 6.8808
fsync time: 18.4634
fsync time: 9.6852
fsync time: 10.6146
fsync time: 8.5015
fsync time: 5.2160
The destination disk did not have any significant IO on it at the time.
The system is running Fedora 10 2.6.27.19-78.2.30.fc9.x86_64 and has two RAID1 arrays attached to an aacraid controller. ext3 filesystems mounted with noatime.
-Dave
Quoted 7 lines · On Tue, 24 Mar 2009 09:20:32 -0400 Theodore Tso <[email protected]> wrote:
They don't solve the problem where there is a *huge* amount of writes going on, though --- if something is dirtying pages at a rate far greater than the local disk can write it out, say, either "dd if=/dev/zero of=/mnt/make-lots-of-writes" or a massive distcc cluster driving a huge amount of data towards a single system or a wget over a local 100 megabit ethernet from a massive NFS server where everything is in cache, then you can have a major delay with the
fsync().
You make it sound like this is hard to do... I was running into this problem *every day* until I moved to XFS recently. I'm running a fairly beefy desktop (VMware running a crappy Windows install w/AV junk on it, builds, icecream and large mailboxes) and have a lot of RAM, but it became unusable for minutes at a time, which was just totally unacceptable, thus the switch. Things have been better since, but are still a little choppy.
I remember early in the 2.6.x days there was a lot of focus on making interactive performance good, and for a long time it was. But this I/O problem has been around for a *long* time now... What happened? Do not many people run into this daily? Do all the filesystem hackers run with special mount options to mitigate the problem?
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Quoted 7 lines · On Tue, 24 Mar 2009 16:03:53 -0700 Jesse Barnes <[email protected]>…
I remember early in the 2.6.x days there was a lot of focus on making interactive performance good, and for a long time it was. But this I/O problem has been around for a *long* time now... What happened? Do not many people run into this daily? Do all the filesystem hackers run with special mount options to mitigate the problem?
the people that care use my kernel patch on ext3 ;-) (or the userland equivalent tweak in /etc/rc.local)
Signature · 3 lines
Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org
Quoted 10 lines · Arjan van de Ven
Quoted 5 lines · On Tue, 24 Mar 2009 16:03:53 -0700 Jesse Barnes <[email protected]>…
I remember early in the 2.6.x days there was a lot of focus on making interactive performance good, and for a long time it was. But this I/O problem has been around for a *long* time now... What happened? Do not many people run into this daily? Do all the filesystem hackers run with special mount options to mitigate the problem?
the people that care use my kernel patch on ext3 ;-) (or the userland equivalent tweak in
/etc/rc.local)
There's a couple of comments in bug 12309 [1] which confirm that increasing the priority of kjournald reduces latency significantly since I posted your tweak there yesterday. I hope to do some testing today on my systems to see if it helps on them, too.
-Dave
Quoted 10 lines · Arjan van de Ven
Quoted 6 lines · On Tue, 24 Mar 2009 16:03:53 -0700 Jesse Barnes <[email protected]>…
I remember early in the 2.6.x days there was a lot of focus on making interactive performance good, and for a long time it was. But this I/O problem has been around for a *long* time now... What happened? Do not many people run into this daily? Do all the filesystem hackers run with special mount options to mitigate the problem?
Quoted 5 lines
the people that care use my kernel patch on ext3 ;-) (or the userland equivalent tweak in
/etc/rc.local)
Ok, I bite what is the userland tweak?
Signature · 5 lines
"They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson)
Quoted 1 line · Stephen Clark
Arjan van de Ven wrote:
..
Quoted 6 lines
Quoted 5 lines
the people that care use my kernel patch on ext3 ;-) (or the userland equivalent tweak in
/etc/rc.local)Ok, I bite what is the userland tweak?
## /etc/rc.local:
for i in pidof kjournald ; do ionice -c1 -p $i ; done
Theodore Tso
maintainerQuoted 9 lines · Jesse Barnes
You make it sound like this is hard to do... I was running into this problem *every day* until I moved to XFS recently. I'm running a fairly beefy desktop (VMware running a crappy Windows install w/AV junk on it, builds, icecream and large mailboxes) and have a lot of RAM, but it became unusable for minutes at a time, which was just totally unacceptable, thus the switch. Things have been better since, but are still a little choppy.
I have 4 gigs of memory on my laptop, and I've never seen it these sorts of issues. So maybe filesystem hackers don't have enough memory; or we don't use the right workloads? It would help if I understood how to trigger these disaster cases. I've had to work *really* hard (as in dd if=/dev/zero of=/mnt/dirty-me-harder) in order to get even a 30 second fsync() delay. So understanding what sort of things you do that cause that many files data blocks to be dirtied, and/or what is causing a major read workload, would be useful.
It may be that we just need to tune the VM to be much more aggressive about pushing dirty pages to the disk sooner. Understanding how the dynamics are working would be the first step.
Quoted 5 lines
I remember early in the 2.6.x days there was a lot of focus on making interactive performance good, and for a long time it was. But this I/O problem has been around for a *long* time now... What happened? Do not many people run into this daily? Do all the filesystem hackers run with special mount options to mitigate the problem?
All I can tell you is that *I* don't run into them, even when I was using ext3 and before I got an SSD in my laptop. I don't understand why; maybe because I don't get really nice toys like systems with 32G's of memory. Or maybe it's because I don't use icecream (whatever that is). What ever it is, it would be useful to get some solid reproduction information, with details about hardware configuration, and information collecting using sar and scripts that gather /proc/meminfo every 5 seconds, and what the applications were doing at the time.
It might also be useful for someone to try reducing the amount of memory the system is using by using mem= on the boot line, and see if that changes things, and to try simplifying the application workload, and/or using iotop to determine what is most contributing to the problem. (And of course, this needs to be done with someone using ext3, since both ext4 and XFS use delayed allocation, which will largely make this problem go away.)
- Ted
Quoted 20 lines · On Tue, 24 Mar 2009 22:09:15 -0400 Theodore Tso <[email protected]> wrote:
Quoted 9 lines · Jesse Barnes
You make it sound like this is hard to do... I was running into this problem *every day* until I moved to XFS recently. I'm running a fairly beefy desktop (VMware running a crappy Windows install w/AV junk on it, builds, icecream and large mailboxes) and have a lot of RAM, but it became unusable for minutes at a time, which was just totally unacceptable, thus the switch. Things have been better since, but are still a little choppy.
I have 4 gigs of memory on my laptop, and I've never seen it these sorts of issues. So maybe filesystem hackers don't have enough memory; or we don't use the right workloads? It would help if I understood how to trigger these disaster cases. I've had to work *really* hard (as in dd if=/dev/zero of=/mnt/dirty-me-harder) in order to get even a 30 second
fsync()delay. So understanding what sort of things you do that cause that many files data blocks to be dirtied, and/or what is causing a major read workload, would be useful.
Quoted 3 lines
It may be that we just need to tune the VM to be much more aggressive about pushing dirty pages to the disk sooner. Understanding how the dynamics are working would be the first step.
Well I think that's part of the problem; this is bigger than just filesystems; I've been using ext3 since before I started seeing this, so it seems like a bad VM/fs interaction may be to blame.
Quoted 7 lines
Quoted 6 lines
I remember early in the 2.6.x days there was a lot of focus on making interactive performance good, and for a long time it was. But this I/O problem has been around for a *long* time now... What happened? Do not many people run into this daily? Do all the filesystem hackers run with special mount options to mitigate the problem?
Quoted 9 lines
All I can tell you is that *I* don't run into them, even when I was using ext3 and before I got an SSD in my laptop. I don't understand why; maybe because I don't get really nice toys like systems with 32G's of memory. Or maybe it's because I don't use icecream (whatever that is). What ever it is, it would be useful to get some solid reproduction information, with details about hardware configuration, and information collecting using sar and scripts that gather
/proc/meminfoevery 5 seconds, and what the applications were doing at the time.
icecream is a distributed compiler system. Like distcc but a bit more cross-compile & heterogeneous compiler friendly.
Quoted 7 lines
It might also be useful for someone to try reducing the amount of memory the system is using by using mem= on the boot line, and see if that changes things, and to try simplifying the application workload, and/or using iotop to determine what is most contributing to the problem. (And of course, this needs to be done with someone using ext3, since both ext4 and XFS use delayed allocation, which will largely make this problem go away.)
Yep, and that's where my blame comes in. I whined about this to a few people, like Arjan, who provided workarounds, but never got beyond that. Some real debugging would be needed to find & fix the root cause(s).
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Am Mittwoch 25 März 2009 schrieb Jesse Barnes:
Quoted 20 lines
On Tue, 24 Mar 2009 09:20:32 -0400
Quoted 8 lines · Theodore Tso
They don't solve the problem where there is a *huge* amount of writes going on, though --- if something is dirtying pages at a rate far greater than the local disk can write it out, say, either "dd if=/dev/zero of=/mnt/make-lots-of-writes" or a massive distcc cluster driving a huge amount of data towards a single system or a wget over a local 100 megabit ethernet from a massive NFS server where everything is in cache, then you can have a major delay with the
fsync().You make it sound like this is hard to do... I was running into this problem *every day* until I moved to XFS recently. I'm running a fairly beefy desktop (VMware running a crappy Windows install w/AV junk on it, builds, icecream and large mailboxes) and have a lot of RAM, but it became unusable for minutes at a time, which was just totally unacceptable, thus the switch. Things have been better since, but are still a little choppy.
Quoted 5 lines
I remember early in the 2.6.x days there was a lot of focus on making interactive performance good, and for a long time it was. But this I/O problem has been around for a *long* time now... What happened? Do not many people run into this daily? Do all the filesystem hackers run with special mount options to mitigate the problem?
Well I always had the feeling that somewhen from one 2.6.x to another I/O latencies increased a lot. But first I thought I was just imaging this and when I more and more thought that this is for real, I forgot since when I observed these increased latencies.
This is on IBM ThinkPad T42 and T23 with XFS.
I/O latencies are pathetic when dpkg reads in the database or I do tar -xf linux-x.y.z.tar.bz2.
I never got down to what is causing these higher latencies though also I tried different I/O schedulers, tuned XFS options, used relatime.
What I found tough is that on XFS at least a tar -xf linux-kernel / rm -rf linux-kernel operation is way slower with barriers and write cache enabled that with no barriers and no write cache enabled. And frankly I never got that.
XFS crawls to a stop on metadata operations when barriers are enabled. According to the XFS FAQ disabling drive write cache should be as safe as enabling barriers. And I always unterstood barriers as a feature to be have *some* ordering contraints, i.e. write before barrier go before barrier and writes after it after it - even when a drives hardware write cache is involved. But when this cache is enabled ordering will always be like issued from Linux block layer cause all I/Os issued to the drive are write-through and synchron without write cache, versus only barrier requests are synchron with barriers and write cache.
Signature · 2 lines
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Quoted 11 lines · Alan Cox
Quoted 6 lines
Quoted 4 lines
I have not had this problem since I applied Arjan's (for some reason repeatedly rejected) patch to change the ioprio of the various writeback daemons. Under some loads changing to the noop I/O scheduler also seems to help (as do most of the non default ones)
(link would be useful)
"Give kjournald a
IOPRIO_CLASS_RTio priority"October 2007 (yes its that old)
One issue discussed back then (also for a similar XFS patch) was that having the kernel use the RT priorities by default makes them useless as user override.
The proposal was to have a new priority level between normal and RT for this, but noone implemented this.
-Andi
Signature · 1 line
[email protected] -- Speaking for myself only.
Quoted 47 lines
Quoted 4 lines · Linus Torvalds
This obviously starts the merge window for 2.6.30, although as usual, I'll probably wait a day or two before I start actively merging. I do that in order to hopefully result in people testing the final plain 2.6.29 a bit more before all the crazy changes start up again.
I know this has been discussed before:
[129401.996244] INFO: task updatedb.mlocat:31092 blocked for more than 480 seconds. [129402.084667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [129402.179331] updatedb.mloc D 0000000000000000 0 31092 31091 [129402.179335] ffff8805ffa1d900 0000000000000082 ffff8803ff5688a8 0000000000001000 [129402.179338] ffffffff806cc000 ffffffff806cc000 ffffffff806d3e80 ffffffff806d3e80 [129402.179341] ffffffff806cfe40 ffffffff806d3e80 ffff8801fb9f87e0 000000000000ffff [129402.179343] Call Trace: [129402.179353] [<ffffffff802d3ff0>] sync_buffer+0x0/0x50 [129402.179358] [<ffffffff80493a50>] io_schedule+0x20/0x30 [129402.179360] [<ffffffff802d402b>] sync_buffer+0x3b/0x50 [129402.179362] [<ffffffff80493d2f>] __wait_on_bit+0x4f/0x80 [129402.179364] [<ffffffff802d3ff0>] sync_buffer+0x0/0x50 [129402.179366] [<ffffffff80493dda>] out_of_line_wait_on_bit+0x7a/0xa0 [129402.179369] [<ffffffff80252730>] wake_bit_function+0x0/0x30 [129402.179396] [<ffffffffa0264346>] ext3_find_entry+0xf6/0x610 [ext3] [129402.179399] [<ffffffff802d3453>] __find_get_block+0x83/0x170 [129402.179403] [<ffffffff802c4a90>] ifind_fast+0x50/0xa0 [129402.179405] [<ffffffff802c5874>] iget_locked+0x44/0x180 [129402.179412] [<ffffffffa0266435>] ext3_lookup+0x55/0x100 [ext3] [129402.179415] [<ffffffff802c32a7>] d_alloc+0x127/0x1c0 [129402.179417] [<ffffffff802ba2a7>] do_lookup+0x1b7/0x250 [129402.179419] [<ffffffff802bc51d>] __link_path_walk+0x76d/0xd60 [129402.179421] [<ffffffff802ba17f>] do_lookup+0x8f/0x250 [129402.179424] [<ffffffff802c8b37>] mntput_no_expire+0x27/0x150 [129402.179426] [<ffffffff802bcb64>] path_walk+0x54/0xb0 [129402.179428] [<ffffffff802bfd10>] filldir+0x0/0xf0 [129402.179430] [<ffffffff802bcc8a>] do_path_lookup+0x7a/0x150 [129402.179432] [<ffffffff802bbb55>] getname+0xe5/0x1f0 [129402.179434] [<ffffffff802bd8d4>] user_path_at+0x44/0x80 [129402.179437] [<ffffffff802b53b5>] cp_new_stat+0xe5/0x100 [129402.179440] [<ffffffff802b56d0>] vfs_lstat_fd+0x20/0x60 [129402.179442] [<ffffffff802b5737>] sys_newlstat+0x27/0x50 [129402.179445] [<ffffffff8020c35b>] system_call_fastpath+0x16/0x1b
Quoted 7 lines
Consensus seems to be something with large memory machines, lots of dirty pages and a long writeout time due to ext3.
At the moment this the largest "usabillity" issue in the serversetup I'm working with. Can there be done something to "autotune" it .. or perhaps even fix it? .. or is it just to shift to xfs or wait for ext4?
Hi Jesper,
What you are seeing looks awefully like the bug I have spent some time to try to figure out in this bugzilla thread :
[Bug 12309] Large I/O operations result in slow performance and high
iowait times
http://bugzilla.kernel.org/show_bug.cgi?id=12309
I created a fio test case out of a lttng trace to reproduce the problem and created a patch to try to account the pages used by the i/o elevator in the vm page count used to calculate memory pressure. Basically, the behavior I was seeing is a constant increase of memory usage when doing a dd-like write to disk until the memory fills up, which is indeed wrong. The patch I posted in that thread seems to cause other problems though, so probably we should teach kjournald to do better.
Here is the patch attempt :
http://bugzilla.kernel.org/attachment.cgi?id=20172
Here is the fio test case :
http://bugzilla.kernel.org/attachment.cgi?id=19894
My findings were this (I hope other people with deeper knowledge of block layer/vm interaction can correct me) :
- Upon heavy and long disk writes, the pages used to back the buffers continuously increase as if there was no memory pressure at all. Therefore, I suspect they are held in a nowhere land that's unaccounted for at the vm layer (not part of memory pressure). That would seem to be the I/O elevator.
Can you give a try at the dd and fio test cases pointed out in the bugzilla entry ? You may also want to see if my patch helps to partially solve your problem. Another hint is to try to use the cgroups to restrict you heavy I/O processes to a limited amount of memory; although it does not solve the core of the problem, it made it disappear for me. And of course trying to get a LTTng trace to get your head around the problem can be very efficient. It's available as a git tree over 2.6.29, and includes VFS, block I/O layer and vm instrumentation, which helps looking at their interaction. All information is at
http://www.lttng.org.
Hoping this helps,
Mathieu
Signature · 2 lines
Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
In reply to Linus TorvaldsYesterday about half of my testboxes (3 out of 7) started getting weird networking failures: their network interface just got stuck completely - no rx and no tx at all. Restarting the interface did not help.
The failures were highly sporadic and not reproducible - they triggered in distcc workloads, and on random kernels and seemingly random .config's.
After spending most of today trying to find a good reproducer (my regular tests werent specific enough to catch it in any bisectable manner), i settled down on 4 parallel instances of TCP traffic:
nohup ssh testbox yes &
nohup ssh testbox yes &
nohup ssh testbox yes &
nohup ssh testbox yes &
[ over gigabit, forcedeth driver. ]
If the box hung within 15 minutes, the kernel was deemed bad. Using that method i arrived to this upstream networking fix which was merged yesterday:
| 303c6a0251852ecbdc5c15e466dcaff5971f7517 is first bad commit | commit 303c6a0251852ecbdc5c15e466dcaff5971f7517 | Author: Herbert Xu <[email protected]> | Date: Tue Mar 17 13:11:29 2009 -0700 | | gro: Fix legacy path napi_complete crash
Applying the straight revert below cured the problem - i now have 10 million packets and 30 minutes of uptime and the box is still fine.
bisection log:
[ 10 iterations ] good: 73bc6e1: Merge branch 'linus'
[ 3 iterations ] bad: 4eac7d0: Merge branch 'irq/threaded'
[ 6.0m packets ] good: e17bbdb: Merge branch 'tracing/core' [ 0.1m packets ] bad: 8e0ee43: Linux 2.6.29 [ 0.1m packets ] bad: e2fc4d1: dca: add missing copyright/license headers [ 0.2m packets ] bad: 4783256: virtio_net: Make virtio_net support carrier detection [ 0.4m packets ] bad: 4ada810: Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf [ 7.0m packets ] good: ec8d540: netfilter: conntrack: fix dropping packet after l4proto->packet() [ 4.0m packets ] good: d1238d5: netfilter: conntrack: check for NEXTHDR_NONE before header sanity checking [ 0.1m packets ] bad: 303c6a0: gro: Fix legacy path napi_complete crash
(the first column is millions of packets tested.)
Looking at this commit also explains the assymetric test pattern i found amongst boxes: all boxes with a new-style NAPI driver (e1000e) work - the others (forcedeth, 5c9x/vortex) have stuck interfaces.
I've attached the reproducer (non-SMP) .config. The system has:
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
[ 34.722154] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.62. [ 34.729406] forcedeth 0000:00:0a.0: setting latency timer to 64 [ 34.735320] nv_probe: set workaround bit for reversed mac addr [ 35.265783] PM: Adding info for No Bus:eth0 [ 35.270877] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:13:d4:dc:41:12 [ 35.279086] forcedeth 0000:00:0a.0: highdma csum timirq gbit lnktim desc-v3 [ 35.286273] initcall init_nic+0x0/0x16 returned 0 after 550966 usecs
( but the bug does not seem to be driver specific - old-style NAPI
seems to be enough to trigger it. )
Please let me know if you need more info or if i can help with testing a different patch. Bisecting it was hard, but testing whether a fix patch does the trick will be a lot easier, as all the testboxes are back in working order now.
Thanks,
Ingo
--- net/core/dev.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
net/core/dev.c +2 -3
@@ -2588,9 +2588,9 @@ static int process_backlog(struct napi_slocal_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +__napi_complete (napi);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();
@@ -2599,7 +2599,6 @@ static int process_backlog(struct napi_snapi_gro_flush (napi); -out:return work; }
#
# Automatically generated make config: don't edit # Linux kernel version: 2.6.29-rc7
# Tue Mar 24 13:47:49 2009
#
# CONFIG_64BIT is not setCONFIG_X86_32=y
# CONFIG_X86_64 is not setCONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_TIME=yCONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=yCONFIG_MMU=yCONFIG_ZONE_DMA=yCONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_IOMAP=yCONFIG_GENERIC_HWEIGHT=yCONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=yCONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#CONFIG_EXPERIMENTAL=yCONFIG_BROKEN_ON_SMP=yCONFIG_LOCK_KERNEL=yCONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=y
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
# CONFIG_POSIX_MQUEUE is not setCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=y
# CONFIG_TASK_DELAY_ACCT is not set
# CONFIG_TASK_XACCT is not set
# CONFIG_AUDIT is not set
#
# RCU Subsystem
#
# CONFIG_CLASSIC_RCU is not set
# CONFIG_TREE_RCU is not setCONFIG_PREEMPT_RCU=yCONFIG_RCU_TRACE=y
# CONFIG_TREE_RCU_TRACE is not setCONFIG_PREEMPT_RCU_TRACE=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_LOG_BUF_SHIFT=20CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=yCONFIG_GROUP_SCHED=y
# CONFIG_FAIR_GROUP_SCHED is not setCONFIG_RT_GROUP_SCHED=yCONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not setCONFIG_CGROUPS=yCONFIG_CGROUP_DEBUG=yCONFIG_CGROUP_NS=yCONFIG_CGROUP_FREEZER=yCONFIG_CGROUP_DEVICE=yCONFIG_CGROUP_CPUACCT=yCONFIG_RESOURCE_COUNTERS=yCONFIG_CGROUP_MEM_RES_CTLR=yCONFIG_MM_OWNER=yCONFIG_SYSFS_DEPRECATED=yCONFIG_SYSFS_DEPRECATED_V2=yCONFIG_RELAY=yCONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_NET_NS is not setCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_CC_OPTIMIZE_FOR_SIZE=yCONFIG_SYSCTL=yCONFIG_EMBEDDED=yCONFIG_UID16=yCONFIG_SYSCTL_SYSCALL=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not setCONFIG_HOTPLUG=yCONFIG_PRINTK=y
# CONFIG_BUG is not setCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_COMPAT_BRK=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_ANON_INODES=yCONFIG_EPOLL=y
# CONFIG_SIGNALFD is not setCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_VM_EVENT_COUNTERS=yCONFIG_PCI_QUIRKS=yCONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not setCONFIG_TRACEPOINTS=yCONFIG_MARKERS=yCONFIG_HAVE_OPROFILE=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_GENERIC_DMA_COHERENT=yCONFIG_SLABINFO=yCONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0
# CONFIG_MODULES is not setCONFIG_BLOCK=yCONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not setCONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set
#
# IO Schedulers
#CONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_AS=y
# CONFIG_IOSCHED_DEADLINE is not setCONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not setCONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not setCONFIG_DEFAULT_IOSCHED="cfq"CONFIG_PREEMPT_NOTIFIERS=yCONFIG_FREEZER=y
#
# Processor type and features
#
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not setCONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not setCONFIG_X86_FIND_SMP_CONFIG=yCONFIG_X86_MPPARSE=y
# CONFIG_X86_PC is not setCONFIG_X86_ELAN=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
# CONFIG_X86_VISWS is not setCONFIG_X86_RDC321X=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not setCONFIG_PARAVIRT_GUEST=y
# CONFIG_VMI is not setCONFIG_KVM_CLOCK=y
# CONFIG_KVM_GUEST is not set
# CONFIG_LGUEST_GUEST is not setCONFIG_PARAVIRT=yCONFIG_PARAVIRT_CLOCK=yCONFIG_PARAVIRT_DEBUG=y
# CONFIG_MEMTEST is not setCONFIG_X86_CPU=yCONFIG_X86_CMPXCHG=yCONFIG_X86_L1_CACHE_SHIFT=4CONFIG_X86_XADD=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_X86_ALIGNMENT_16=yCONFIG_X86_MINIMUM_CPU_FAMILY=4CONFIG_X86_DEBUGCTLMSR=yCONFIG_PROCESSOR_SELECT=yCONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_CYRIX_32=y
# CONFIG_CPU_SUP_AMD is not setCONFIG_CPU_SUP_CENTAUR_32=y
# CONFIG_CPU_SUP_TRANSMETA_32 is not setCONFIG_CPU_SUP_UMC_32=yCONFIG_X86_DS=yCONFIG_X86_PTRACE_BTS=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
# CONFIG_IOMMU_API is not setCONFIG_NR_CPUS=1
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not setCONFIG_PREEMPT=yCONFIG_X86_UP_APIC=y
# CONFIG_X86_UP_IOAPIC is not setCONFIG_X86_LOCAL_APIC=yCONFIG_X86_MCE=yCONFIG_X86_MCE_NONFATAL=yCONFIG_X86_MCE_P4THERMAL=y
# CONFIG_VM86 is not set
# CONFIG_TOSHIBA is not setCONFIG_I8K=yCONFIG_X86_REBOOTFIXUPS=yCONFIG_MICROCODE=yCONFIG_MICROCODE_INTEL=yCONFIG_MICROCODE_AMD=yCONFIG_MICROCODE_OLD_INTERFACE=yCONFIG_X86_MSR=y
# CONFIG_X86_CPUID is not set
# CONFIG_NOHIGHMEM is not setCONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
# CONFIG_VMSPLIT_3G is not set
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not setCONFIG_VMSPLIT_1G=yCONFIG_PAGE_OFFSET=0x40000000CONFIG_HIGHMEM=y
# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not setCONFIG_SELECT_MEMORY_MODEL=yCONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not setCONFIG_FLATMEM=yCONFIG_FLAT_NODE_MEM_MAP=yCONFIG_PAGEFLAGS_EXTENDED=yCONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_PHYS_ADDR_T_64BIT is not setCONFIG_ZONE_DMA_FLAG=1CONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=yCONFIG_UNEVICTABLE_LRU=yCONFIG_MMU_NOTIFIER=yCONFIG_HIGHPTE=y
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
# CONFIG_X86_RESERVE_LOW_64K is not set
# CONFIG_MATH_EMULATION is not setCONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not setCONFIG_X86_PAT=yCONFIG_SECCOMP=yCONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not setCONFIG_HZ=100
# CONFIG_SCHED_HRTICK is not setCONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not setCONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not setCONFIG_PHYSICAL_ALIGN=0x100000CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not setCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
# Power management and ACPI options
#CONFIG_PM=yCONFIG_PM_DEBUG=yCONFIG_PM_VERBOSE=yCONFIG_CAN_PM_TRACE=yCONFIG_PM_TRACE=yCONFIG_PM_TRACE_RTC=yCONFIG_PM_SLEEP=yCONFIG_SUSPEND=y
# CONFIG_PM_TEST_SUSPEND is not setCONFIG_SUSPEND_FREEZER=y
# CONFIG_ACPI is not setCONFIG_X86_APM_BOOT=yCONFIG_APM=yCONFIG_APM_IGNORE_USER_SUSPEND=yCONFIG_APM_DO_ENABLE=yCONFIG_APM_CPU_IDLE=yCONFIG_APM_DISPLAY_BLANK=yCONFIG_APM_ALLOW_INTS=y
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not setCONFIG_CPU_IDLE=yCONFIG_CPU_IDLE_GOV_LADDER=y
#
# Bus options (PCI etc.)
#CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not setCONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOOLPC is not set
# CONFIG_PCI_GOANY is not setCONFIG_PCI_DIRECT=yCONFIG_PCI_DOMAINS=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_ARCH_SUPPORTS_MSI is not setCONFIG_PCI_LEGACY=yCONFIG_PCI_DEBUG=yCONFIG_PCI_STUB=yCONFIG_ISA_DMA_API=y
# CONFIG_ISA is not setCONFIG_MCA=yCONFIG_MCA_LEGACY=y
# CONFIG_MCA_PROC_FS is not set
# CONFIG_SCx200 is not set
# CONFIG_OLPC is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats / Emulations
#CONFIG_BINFMT_ELF=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_HAVE_AOUT=yCONFIG_BINFMT_AOUT=y
# CONFIG_BINFMT_MISC is not setCONFIG_HAVE_ATOMIC_IOMAP=yCONFIG_NET=y
#
# Networking options
#CONFIG_COMPAT_NET_DEV_OPS=yCONFIG_PACKET=yCONFIG_PACKET_MMAP=yCONFIG_UNIX=yCONFIG_XFRM=yCONFIG_XFRM_USER=yCONFIG_XFRM_SUB_POLICY=yCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_IPCOMP=yCONFIG_NET_KEY=yCONFIG_NET_KEY_MIGRATE=yCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not setCONFIG_IP_FIB_HASH=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=yCONFIG_IP_PNP_BOOTP=yCONFIG_IP_PNP_RARP=yCONFIG_NET_IPIP=y
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not setCONFIG_SYN_COOKIES=yCONFIG_INET_AH=y
# CONFIG_INET_ESP is not setCONFIG_INET_IPCOMP=yCONFIG_INET_XFRM_TUNNEL=yCONFIG_INET_TUNNEL=yCONFIG_INET_XFRM_MODE_TRANSPORT=y
# CONFIG_INET_XFRM_MODE_TUNNEL is not setCONFIG_INET_XFRM_MODE_BEET=yCONFIG_INET_LRO=yCONFIG_INET_DIAG=yCONFIG_INET_TCP_DIAG=yCONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not setCONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not setCONFIG_TCP_CONG_HYBLA=yCONFIG_TCP_CONG_VEGAS=yCONFIG_TCP_CONG_SCALABLE=y
# CONFIG_TCP_CONG_LP is not setCONFIG_TCP_CONG_VENO=yCONFIG_TCP_CONG_YEAH=yCONFIG_TCP_CONG_ILLINOIS=y
# CONFIG_DEFAULT_BIC is not setCONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not setCONFIG_DEFAULT_TCP_CONG="cubic"CONFIG_TCP_MD5SIG=y
# CONFIG_IPV6 is not setCONFIG_NETLABEL=yCONFIG_NETWORK_SECMARK=yCONFIG_NETFILTER=yCONFIG_NETFILTER_DEBUG=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#CONFIG_NETFILTER_NETLINK=yCONFIG_NETFILTER_NETLINK_QUEUE=y
# CONFIG_NETFILTER_NETLINK_LOG is not setCONFIG_NF_CONNTRACK=yCONFIG_NF_CT_ACCT=y
# CONFIG_NF_CONNTRACK_MARK is not setCONFIG_NF_CONNTRACK_SECMARK=y
# CONFIG_NF_CONNTRACK_EVENTS is not set
# CONFIG_NF_CT_PROTO_DCCP is not setCONFIG_NF_CT_PROTO_GRE=yCONFIG_NF_CT_PROTO_SCTP=yCONFIG_NF_CT_PROTO_UDPLITE=y
# CONFIG_NF_CONNTRACK_AMANDA is not setCONFIG_NF_CONNTRACK_FTP=yCONFIG_NF_CONNTRACK_H323=yCONFIG_NF_CONNTRACK_IRC=yCONFIG_NF_CONNTRACK_NETBIOS_NS=yCONFIG_NF_CONNTRACK_PPTP=yCONFIG_NF_CONNTRACK_SANE=yCONFIG_NF_CONNTRACK_SIP=yCONFIG_NF_CONNTRACK_TFTP=yCONFIG_NF_CT_NETLINK=yCONFIG_NETFILTER_TPROXY=yCONFIG_NETFILTER_XTABLES=yCONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
# CONFIG_NETFILTER_XT_TARGET_CONNMARK is not setCONFIG_NETFILTER_XT_TARGET_CONNSECMARK=yCONFIG_NETFILTER_XT_TARGET_DSCP=yCONFIG_NETFILTER_XT_TARGET_MARK=y
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
# CONFIG_NETFILTER_XT_TARGET_NOTRACK is not setCONFIG_NETFILTER_XT_TARGET_RATEEST=yCONFIG_NETFILTER_XT_TARGET_TPROXY=y
# CONFIG_NETFILTER_XT_TARGET_TRACE is not setCONFIG_NETFILTER_XT_TARGET_SECMARK=y
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not setCONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=y
# CONFIG_NETFILTER_XT_MATCH_COMMENT is not setCONFIG_NETFILTER_XT_MATCH_CONNBYTES=y
# CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_CONNMARK is not setCONFIG_NETFILTER_XT_MATCH_CONNTRACK=yCONFIG_NETFILTER_XT_MATCH_DCCP=yCONFIG_NETFILTER_XT_MATCH_DSCP=y
# CONFIG_NETFILTER_XT_MATCH_ESP is not setCONFIG_NETFILTER_XT_MATCH_HASHLIMIT=y
# CONFIG_NETFILTER_XT_MATCH_HELPER is not setCONFIG_NETFILTER_XT_MATCH_IPRANGE=y
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not setCONFIG_NETFILTER_XT_MATCH_LIMIT=yCONFIG_NETFILTER_XT_MATCH_MAC=yCONFIG_NETFILTER_XT_MATCH_MARK=y
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not setCONFIG_NETFILTER_XT_MATCH_OWNER=y
# CONFIG_NETFILTER_XT_MATCH_POLICY is not setCONFIG_NETFILTER_XT_MATCH_PHYSDEV=y
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not setCONFIG_NETFILTER_XT_MATCH_QUOTA=yCONFIG_NETFILTER_XT_MATCH_RATEEST=yCONFIG_NETFILTER_XT_MATCH_REALM=y
# CONFIG_NETFILTER_XT_MATCH_RECENT is not setCONFIG_NETFILTER_XT_MATCH_SCTP=yCONFIG_NETFILTER_XT_MATCH_SOCKET=yCONFIG_NETFILTER_XT_MATCH_STATE=yCONFIG_NETFILTER_XT_MATCH_STATISTIC=y
# CONFIG_NETFILTER_XT_MATCH_STRING is not set
# CONFIG_NETFILTER_XT_MATCH_TCPMSS is not setCONFIG_NETFILTER_XT_MATCH_TIME=y
# CONFIG_NETFILTER_XT_MATCH_U32 is not setCONFIG_IP_VS=y
# CONFIG_IP_VS_DEBUG is not setCONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
# CONFIG_IP_VS_PROTO_TCP is not setCONFIG_IP_VS_PROTO_UDP=yCONFIG_IP_VS_PROTO_AH_ESP=yCONFIG_IP_VS_PROTO_ESP=yCONFIG_IP_VS_PROTO_AH=y
#
# IPVS scheduler
#
# CONFIG_IP_VS_RR is not setCONFIG_IP_VS_WRR=y
# CONFIG_IP_VS_LC is not setCONFIG_IP_VS_WLC=yCONFIG_IP_VS_LBLC=yCONFIG_IP_VS_LBLCR=yCONFIG_IP_VS_DH=yCONFIG_IP_VS_SH=yCONFIG_IP_VS_SED=yCONFIG_IP_VS_NQ=y
#
# IPVS application helper
#
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=y
# CONFIG_NF_CONNTRACK_IPV4 is not setCONFIG_IP_NF_QUEUE=yCONFIG_IP_NF_IPTABLES=y
# CONFIG_IP_NF_MATCH_ADDRTYPE is not setCONFIG_IP_NF_MATCH_AH=yCONFIG_IP_NF_MATCH_ECN=yCONFIG_IP_NF_MATCH_TTL=yCONFIG_IP_NF_FILTER=yCONFIG_IP_NF_TARGET_REJECT=y
# CONFIG_IP_NF_TARGET_LOG is not setCONFIG_IP_NF_TARGET_ULOG=yCONFIG_IP_NF_MANGLE=y
# CONFIG_IP_NF_TARGET_ECN is not set
# CONFIG_IP_NF_TARGET_TTL is not setCONFIG_IP_NF_RAW=y
# CONFIG_IP_NF_SECURITY is not set
# CONFIG_IP_NF_ARPTABLES is not set
#
# DECnet: Netfilter Configuration
#CONFIG_DECNET_NF_GRABULATOR=yCONFIG_BRIDGE_NF_EBTABLES=y
# CONFIG_BRIDGE_EBT_BROUTE is not setCONFIG_BRIDGE_EBT_T_FILTER=y
# CONFIG_BRIDGE_EBT_T_NAT is not set
# CONFIG_BRIDGE_EBT_802_3 is not setCONFIG_BRIDGE_EBT_AMONG=y
# CONFIG_BRIDGE_EBT_ARP is not setCONFIG_BRIDGE_EBT_IP=yCONFIG_BRIDGE_EBT_LIMIT=yCONFIG_BRIDGE_EBT_MARK=yCONFIG_BRIDGE_EBT_PKTTYPE=yCONFIG_BRIDGE_EBT_STP=yCONFIG_BRIDGE_EBT_VLAN=yCONFIG_BRIDGE_EBT_ARPREPLY=yCONFIG_BRIDGE_EBT_DNAT=yCONFIG_BRIDGE_EBT_MARK_T=yCONFIG_BRIDGE_EBT_REDIRECT=yCONFIG_BRIDGE_EBT_SNAT=yCONFIG_BRIDGE_EBT_LOG=yCONFIG_BRIDGE_EBT_ULOG=yCONFIG_BRIDGE_EBT_NFLOG=yCONFIG_IP_DCCP=yCONFIG_INET_DCCP_DIAG=y
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#CONFIG_IP_DCCP_CCID2_DEBUG=y
# CONFIG_IP_DCCP_CCID3 is not set
#
# DCCP Kernel Hacking
#CONFIG_IP_DCCP_DEBUG=yCONFIG_IP_SCTP=y
# CONFIG_SCTP_DBG_MSG is not setCONFIG_SCTP_DBG_OBJCNT=yCONFIG_SCTP_HMAC_NONE=y
# CONFIG_SCTP_HMAC_SHA1 is not set
# CONFIG_SCTP_HMAC_MD5 is not set
# CONFIG_TIPC is not setCONFIG_ATM=yCONFIG_ATM_CLIP=yCONFIG_ATM_CLIP_NO_ICMP=yCONFIG_ATM_LANE=yCONFIG_ATM_MPOA=yCONFIG_ATM_BR2684=yCONFIG_ATM_BR2684_IPFILTER=yCONFIG_STP=yCONFIG_BRIDGE=yCONFIG_NET_DSA=yCONFIG_NET_DSA_TAG_DSA=yCONFIG_NET_DSA_TAG_EDSA=yCONFIG_NET_DSA_TAG_TRAILER=yCONFIG_NET_DSA_MV88E6XXX=yCONFIG_NET_DSA_MV88E6060=yCONFIG_NET_DSA_MV88E6XXX_NEED_PPU=yCONFIG_NET_DSA_MV88E6131=yCONFIG_NET_DSA_MV88E6123_61_65=y
# CONFIG_VLAN_8021Q is not setCONFIG_DECNET=yCONFIG_DECNET_ROUTER=yCONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not setCONFIG_X25=yCONFIG_LAPB=y
# CONFIG_ECONET is not setCONFIG_WAN_ROUTER=y
# CONFIG_NET_SCHED is not setCONFIG_NET_CLS_ROUTE=y
# CONFIG_DCB is not set
#
# Network testing
#CONFIG_NET_PKTGEN=y
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not setCONFIG_IRDA=y
#
# IrDA protocols
#CONFIG_IRLAN=yCONFIG_IRNET=yCONFIG_IRCOMM=y
# CONFIG_IRDA_ULTRA is not set
#
# IrDA options
#
# CONFIG_IRDA_CACHE_LAST_LSAP is not setCONFIG_IRDA_FAST_RR=yCONFIG_IRDA_DEBUG=y
#
# Infrared-port device drivers
#
#
# SIR device drivers
#
# CONFIG_IRTTY_SIR is not set
#
# Dongle support
#CONFIG_KINGSUN_DONGLE=y
# CONFIG_KSDAZZLE_DONGLE is not set
# CONFIG_KS959_DONGLE is not set
#
# FIR device drivers
#
# CONFIG_USB_IRDA is not set
# CONFIG_SIGMATEL_FIR is not setCONFIG_NSC_FIR=yCONFIG_WINBOND_FIR=y
# CONFIG_TOSHIBA_FIR is not setCONFIG_SMC_IRCC_FIR=yCONFIG_ALI_FIR=yCONFIG_VLSI_FIR=yCONFIG_VIA_FIR=yCONFIG_MCS_FIR=yCONFIG_BT=yCONFIG_BT_L2CAP=yCONFIG_BT_SCO=yCONFIG_BT_RFCOMM=yCONFIG_BT_RFCOMM_TTY=yCONFIG_BT_BNEP=yCONFIG_BT_BNEP_MC_FILTER=yCONFIG_BT_BNEP_PROTO_FILTER=y
# CONFIG_BT_HIDP is not set
#
# Bluetooth device drivers
#CONFIG_BT_HCIBTUSB=yCONFIG_BT_HCIBTSDIO=yCONFIG_BT_HCIUART=yCONFIG_BT_HCIUART_H4=y
# CONFIG_BT_HCIUART_BCSP is not setCONFIG_BT_HCIUART_LL=yCONFIG_BT_HCIBCM203X=yCONFIG_BT_HCIBPA10X=yCONFIG_BT_HCIBFUSB=y
# CONFIG_BT_HCIVHCI is not set
# CONFIG_AF_RXRPC is not setCONFIG_PHONET=yCONFIG_FIB_RULES=y
# CONFIG_WIRELESS is not setCONFIG_WIRELESS_EXT=yCONFIG_LIB80211=yCONFIG_LIB80211_CRYPT_WEP=yCONFIG_LIB80211_CRYPT_CCMP=yCONFIG_LIB80211_CRYPT_TKIP=yCONFIG_WIMAX=yCONFIG_WIMAX_DEBUG_LEVEL=8
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"CONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=yCONFIG_FW_LOADER=yCONFIG_FIRMWARE_IN_KERNEL=yCONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not setCONFIG_DEBUG_DEVRES=y
# CONFIG_SYS_HYPERVISOR is not setCONFIG_CONNECTOR=yCONFIG_PROC_EVENTS=y
# CONFIG_MTD is not setCONFIG_PARPORT=yCONFIG_PARPORT_PC=yCONFIG_PARPORT_SERIAL=yCONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not setCONFIG_PARPORT_AX88796=y
# CONFIG_PARPORT_1284 is not setCONFIG_PARPORT_NOT_PC=yCONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not setCONFIG_BLK_CPQ_DA=yCONFIG_BLK_CPQ_CISS_DA=y
# CONFIG_CISS_SCSI_TAPE is not setCONFIG_BLK_DEV_DAC960=y
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not setCONFIG_BLK_DEV_LOOP=yCONFIG_BLK_DEV_CRYPTOLOOP=yCONFIG_BLK_DEV_NBD=yCONFIG_BLK_DEV_SX8=yCONFIG_BLK_DEV_UB=yCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=4096CONFIG_BLK_DEV_XIP=yCONFIG_CDROM_PKTCDVD=yCONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_VIRTIO_BLK is not set
# CONFIG_BLK_DEV_HD is not set
# CONFIG_MISC_DEVICES is not setCONFIG_TIFM_CORE=yCONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not setCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_TGT=yCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=yCONFIG_CHR_DEV_ST=yCONFIG_CHR_DEV_OSST=yCONFIG_BLK_DEV_SR=yCONFIG_BLK_DEV_SR_VENDOR=y
# CONFIG_CHR_DEV_SG is not setCONFIG_CHR_DEV_SCH=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs #CONFIG_SCSI_MULTI_LUN=yCONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set CONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=yCONFIG_SCSI_FC_ATTRS=yCONFIG_SCSI_FC_TGT_ATTRS=yCONFIG_SCSI_ISCSI_ATTRS=y
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not setCONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not setCONFIG_SCSI_CXGB3_ISCSI=yCONFIG_BLK_DEV_3W_XXXX_RAID=yCONFIG_SCSI_3W_9XXX=yCONFIG_SCSI_ACARD=yCONFIG_SCSI_AACRAID=yCONFIG_SCSI_AIC7XXX=yCONFIG_AIC7XXX_CMDS_PER_DEVICE=32CONFIG_AIC7XXX_RESET_DELAY_MS=5000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not setCONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC7XXX_OLD is not setCONFIG_SCSI_AIC79XX=yCONFIG_AIC79XX_CMDS_PER_DEVICE=32CONFIG_AIC79XX_RESET_DELAY_MS=5000CONFIG_AIC79XX_DEBUG_ENABLE=yCONFIG_AIC79XX_DEBUG_MASK=0CONFIG_AIC79XX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not setCONFIG_SCSI_ARCMSR=y
# CONFIG_MEGARAID_NEWGEN is not setCONFIG_MEGARAID_LEGACY=y
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not setCONFIG_LIBFC=yCONFIG_FCOE=yCONFIG_SCSI_DMX3191D=y
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_FD_MCS is not setCONFIG_SCSI_GDTH=yCONFIG_SCSI_IBMMCA=yCONFIG_IBMMCA_SCSI_ORDER_STANDARD=yCONFIG_IBMMCA_SCSI_DEV_RESET=yCONFIG_SCSI_IPS=y
# CONFIG_SCSI_INITIO is not setCONFIG_SCSI_INIA100=y
# CONFIG_SCSI_PPA is not setCONFIG_SCSI_IMM=yCONFIG_SCSI_IZIP_EPP16=y
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_SCSI_MVSAS is not setCONFIG_SCSI_NCR_D700=yCONFIG_SCSI_STEX=y
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not setCONFIG_SCSI_NCR_Q720=yCONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_QLOGIC_1280 is not setCONFIG_SCSI_QLA_FC=yCONFIG_SCSI_QLA_ISCSI=yCONFIG_SCSI_LPFC=yCONFIG_SCSI_LPFC_DEBUG_FS=yCONFIG_SCSI_SIM710=y
CONFIG_SCSI_DC395x=y
# CONFIG_SCSI_DC390T is not setCONFIG_SCSI_NSP32=y
# CONFIG_SCSI_DEBUG is not setCONFIG_SCSI_SRP=yCONFIG_SCSI_DH=yCONFIG_SCSI_DH_RDAC=y
# CONFIG_SCSI_DH_HP_SW is not setCONFIG_SCSI_DH_EMC=y
# CONFIG_SCSI_DH_ALUA is not setCONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not setCONFIG_SATA_PMP=yCONFIG_SATA_AHCI=yCONFIG_SATA_SIL24=yCONFIG_ATA_SFF=yCONFIG_SATA_SVW=yCONFIG_ATA_PIIX=yCONFIG_SATA_MV=yCONFIG_SATA_NV=yCONFIG_PDC_ADMA=yCONFIG_SATA_QSTOR=yCONFIG_SATA_PROMISE=yCONFIG_SATA_SX4=yCONFIG_SATA_SIL=yCONFIG_SATA_SIS=yCONFIG_SATA_ULI=y
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not setCONFIG_SATA_INIC162X=yCONFIG_PATA_ALI=yCONFIG_PATA_AMD=y
# CONFIG_PATA_ARTOP is not setCONFIG_PATA_ATIIXP=yCONFIG_PATA_CMD640_PCI=y
# CONFIG_PATA_CMD64X is not setCONFIG_PATA_CS5520=y
# CONFIG_PATA_CS5530 is not setCONFIG_PATA_CS5535=yCONFIG_PATA_CS5536=yCONFIG_PATA_CYPRESS=yCONFIG_PATA_EFAR=yCONFIG_ATA_GENERIC=yCONFIG_PATA_HPT366=y
# CONFIG_PATA_HPT37X is not setCONFIG_PATA_HPT3X2N=yCONFIG_PATA_HPT3X3=yCONFIG_PATA_HPT3X3_DMA=yCONFIG_PATA_IT821X=y
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not setCONFIG_PATA_TRIFLEX=y
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not setCONFIG_PATA_OLDPIIX=y
# CONFIG_PATA_NETCELL is not setCONFIG_PATA_NINJA32=yCONFIG_PATA_NS87410=y
# CONFIG_PATA_NS87415 is not setCONFIG_PATA_OPTI=yCONFIG_PATA_OPTIDMA=yCONFIG_PATA_PDC_OLD=yCONFIG_PATA_RADISYS=y
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not setCONFIG_PATA_PDC2027X=y
# CONFIG_PATA_SIL680 is not setCONFIG_PATA_SIS=y
# CONFIG_PATA_VIA is not setCONFIG_PATA_WINBOND=yCONFIG_PATA_PLATFORM=y
# CONFIG_PATA_SCH is not setCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=y
# CONFIG_MD_LINEAR is not setCONFIG_MD_RAID0=y
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not setCONFIG_MD_MULTIPATH=yCONFIG_MD_FAULTY=yCONFIG_BLK_DEV_DM=yCONFIG_DM_DEBUG=yCONFIG_DM_CRYPT=y
# CONFIG_DM_SNAPSHOT is not setCONFIG_DM_MIRROR=y
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not setCONFIG_DM_DELAY=y
# CONFIG_DM_UEVENT is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
#
# Enable only one of the two stacks, unless you know what you are doing #CONFIG_FIREWIRE=yCONFIG_FIREWIRE_OHCI=yCONFIG_FIREWIRE_OHCI_DEBUG=y
# CONFIG_FIREWIRE_SBP2 is not setCONFIG_IEEE1394=yCONFIG_IEEE1394_OHCI1394=yCONFIG_IEEE1394_PCILYNX=yCONFIG_IEEE1394_SBP2=yCONFIG_IEEE1394_SBP2_PHYS_DMA=y CONFIG_IEEE1394_ETH1394_ROM_ENTRY=y CONFIG_IEEE1394_ETH1394=yCONFIG_IEEE1394_RAWIO=yCONFIG_IEEE1394_VIDEO1394=y
# CONFIG_IEEE1394_DV1394 is not set CONFIG_IEEE1394_VERBOSEDEBUG=yCONFIG_I2O=y
# CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set
# CONFIG_I2O_EXT_ADAPTEC is not set
# CONFIG_I2O_CONFIG is not set
# CONFIG_I2O_BUS is not set
# CONFIG_I2O_BLOCK is not setCONFIG_I2O_SCSI=yCONFIG_I2O_PROC=y
# CONFIG_MACINTOSH_DRIVERS is not setCONFIG_NETDEVICES=yCONFIG_DUMMY=yCONFIG_BONDING=yCONFIG_MACVLAN=yCONFIG_EQUALIZER=yCONFIG_TUN=yCONFIG_VETH=y
# CONFIG_ARCNET is not setCONFIG_PHYLIB=y
#
# MII PHY device drivers
#CONFIG_MARVELL_PHY=y
# CONFIG_DAVICOM_PHY is not set CONFIG_QSEMI_PHY=yCONFIG_LXT_PHY=yCONFIG_CICADA_PHY=y
# CONFIG_VITESSE_PHY is not set CONFIG_SMSC_PHY=y
# CONFIG_BROADCOM_PHY is not set CONFIG_ICPLUS_PHY=yCONFIG_REALTEK_PHY=y
# CONFIG_NATIONAL_PHY is not set CONFIG_STE10XP=yCONFIG_LSI_ET1011C_PHY=y
# CONFIG_FIXED_PHY is not set CONFIG_MDIO_BITBANG=yCONFIG_MDIO_GPIO=yCONFIG_NET_ETHERNET=yCONFIG_MII=yCONFIG_HAPPYMEAL=yCONFIG_SUNGEM=yCONFIG_CASSINI=y
# CONFIG_NET_VENDOR_3COM is not set CONFIG_NET_VENDOR_SMC=yCONFIG_ULTRAMCA=yCONFIG_ENC28J60=y
# CONFIG_ENC28J60_WRITEVERIFY is not set
# CONFIG_DNET is not set
# CONFIG_NET_TULIP is not set CONFIG_AT1700=y
# CONFIG_DEPCA is not setCONFIG_HP100=yCONFIG_NE2_MCA=yCONFIG_IBMLANA=y
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set CONFIG_ADAPTEC_STARFIRE=y
# CONFIG_B44 is not setCONFIG_FORCEDETH=y
# CONFIG_FORCEDETH_NAPI is not set CONFIG_E100=yCONFIG_FEALNX=y
# CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=y
# CONFIG_8139CP is not set CONFIG_8139TOO=yCONFIG_8139TOO_PIO=y CONFIG_8139TOO_TUNE_TWISTER=y CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set CONFIG_R6040=yCONFIG_SIS900=yCONFIG_EPIC100=yCONFIG_SMSC9420=yCONFIG_SUNDANCE=yCONFIG_SUNDANCE_MMIO=y
# CONFIG_TLAN is not set CONFIG_VIA_RHINE=y
# CONFIG_VIA_RHINE_MMIO is not set
# CONFIG_SC92031 is not set
# CONFIG_NET_POCKET is not set CONFIG_ATL2=yCONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not setCONFIG_DL2K=yCONFIG_E1000=yCONFIG_E1000E=yCONFIG_IP1000=yCONFIG_IGB=yCONFIG_IGB_LRO=yCONFIG_NS83820=yCONFIG_HAMACHI=yCONFIG_YELLOWFIN=yCONFIG_R8169=yCONFIG_SIS190=y
# CONFIG_SKGE is not setCONFIG_SKY2=y
# CONFIG_SKY2_DEBUG is not set
# CONFIG_VIA_VELOCITY is not set CONFIG_TIGON3=yCONFIG_BNX2=yCONFIG_QLA3XXX=y
# CONFIG_ATL1 is not setCONFIG_ATL1E=y
# CONFIG_ATL1C is not setCONFIG_JME=yCONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set CONFIG_CHELSIO_T3_DEPENDS=y CONFIG_CHELSIO_T3=y
# CONFIG_ENIC is not setCONFIG_IXGBE=yCONFIG_IXGB=y
# CONFIG_S2IO is not setCONFIG_MYRI10GE=y
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set CONFIG_TEHUTI=yCONFIG_BNX2X=yCONFIG_QLGE=yCONFIG_SFC=yCONFIG_BE2NET=yCONFIG_TR=yCONFIG_IBMTR=y
# CONFIG_IBMOL is not setCONFIG_IBMLS=yCONFIG_3C359=y
# CONFIG_TMS380TR is not set
# CONFIG_SMCTR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not setCONFIG_WLAN_80211=y
# CONFIG_LIBERTAS is not set
# CONFIG_AIRO is not setCONFIG_HERMES=y
# CONFIG_HERMES_CACHE_FW_ON_INIT is not set
# CONFIG_PLX_HERMES is not setCONFIG_TMD_HERMES=yCONFIG_NORTEL_HERMES=y
# CONFIG_PCI_HERMES is not setCONFIG_ATMEL=y
# CONFIG_PCI_ATMEL is not setCONFIG_PRISM54=yCONFIG_USB_ZD1201=y
# CONFIG_USB_NET_RNDIS_WLAN is not setCONFIG_IPW2100=yCONFIG_IPW2100_MONITOR=yCONFIG_IPW2100_DEBUG=y
# CONFIG_IPW2200 is not setCONFIG_LIBIPW=y
# CONFIG_LIBIPW_DEBUG is not set
# CONFIG_IWLWIFI_LEDS is not set
# CONFIG_HOSTAP is not set
#
# WiMAX Wireless Broadband devices
#CONFIG_WIMAX_I2400M=y
# CONFIG_WIMAX_I2400M_USB is not setCONFIG_WIMAX_I2400M_SDIO=yCONFIG_WIMAX_I2400M_DEBUG_LEVEL=8
#
# USB Network Adapters
#CONFIG_USB_CATC=y
# CONFIG_USB_KAWETH is not setCONFIG_USB_PEGASUS=y
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not setCONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not setCONFIG_ATM_TCP=yCONFIG_ATM_LANAI=y
# CONFIG_ATM_ENI is not setCONFIG_ATM_FIRESTREAM=yCONFIG_ATM_ZATM=yCONFIG_ATM_ZATM_DEBUG=y
# CONFIG_ATM_NICSTAR is not setCONFIG_ATM_IDT77252=yCONFIG_ATM_IDT77252_DEBUG=y
# CONFIG_ATM_IDT77252_RCV_ALL is not setCONFIG_ATM_IDT77252_USE_SUNI=yCONFIG_ATM_AMBASSADOR=yCONFIG_ATM_AMBASSADOR_DEBUG=y
# CONFIG_ATM_HORIZON is not setCONFIG_ATM_IA=y
# CONFIG_ATM_IA_DEBUG is not set
# CONFIG_ATM_FORE200E is not setCONFIG_ATM_HE=yCONFIG_ATM_HE_USE_SUNI=yCONFIG_ATM_SOLOS=y
# CONFIG_FDDI is not setCONFIG_HIPPI=y
# CONFIG_ROADRUNNER is not set
# CONFIG_PLIP is not setCONFIG_PPP=yCONFIG_PPP_MULTILINK=y
# CONFIG_PPP_FILTER is not setCONFIG_PPP_ASYNC=yCONFIG_PPP_SYNC_TTY=yCONFIG_PPP_DEFLATE=yCONFIG_PPP_BSDCOMP=yCONFIG_PPP_MPPE=y
# CONFIG_PPPOE is not setCONFIG_PPPOATM=yCONFIG_PPPOL2TP=yCONFIG_SLIP=yCONFIG_SLIP_COMPRESSED=yCONFIG_SLHC=y
# CONFIG_SLIP_SMART is not set
# CONFIG_SLIP_MODE_SLIP6 is not setCONFIG_NET_FC=yCONFIG_NETCONSOLE=yCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not setCONFIG_NET_POLL_CONTROLLER=yCONFIG_VIRTIO_NET=yCONFIG_ISDN=y
# CONFIG_MISDN is not set
# CONFIG_ISDN_I4L is not set
# CONFIG_ISDN_CAPI is not setCONFIG_PHONE=y
# CONFIG_PHONE_IXJ is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_FF_MEMLESS=yCONFIG_INPUT_POLLDEV=y
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=yCONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ATKBD=yCONFIG_KEYBOARD_SUNKBD=yCONFIG_KEYBOARD_LKKBD=yCONFIG_KEYBOARD_XTKBD=yCONFIG_KEYBOARD_NEWTON=yCONFIG_KEYBOARD_STOWAWAY=yCONFIG_KEYBOARD_GPIO=yCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_PS2_ALPS is not setCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_LIFEBOOK=yCONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not setCONFIG_MOUSE_PS2_TOUCHKIT=yCONFIG_MOUSE_SERIAL=yCONFIG_MOUSE_APPLETOUCH=yCONFIG_MOUSE_BCM5974=y
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not setCONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not setCONFIG_JOYSTICK_A3D=yCONFIG_JOYSTICK_ADI=yCONFIG_JOYSTICK_COBRA=yCONFIG_JOYSTICK_GF2K=yCONFIG_JOYSTICK_GRIP=yCONFIG_JOYSTICK_GRIP_MP=yCONFIG_JOYSTICK_GUILLEMOT=yCONFIG_JOYSTICK_INTERACT=y
# CONFIG_JOYSTICK_SIDEWINDER is not setCONFIG_JOYSTICK_TMDC=y
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not setCONFIG_JOYSTICK_STINGER=y
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not setCONFIG_JOYSTICK_DB9=yCONFIG_JOYSTICK_GAMECON=yCONFIG_JOYSTICK_TURBOGRAFX=y
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not setCONFIG_INPUT_TABLET=y
# CONFIG_TABLET_USB_ACECAD is not setCONFIG_TABLET_USB_AIPTEK=y
# CONFIG_TABLET_USB_GTCO is not setCONFIG_TABLET_USB_KBTAB=yCONFIG_TABLET_USB_WACOM=y
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=yCONFIG_SERIO_CT82C710=yCONFIG_SERIO_PARKBD=y
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not setCONFIG_GAMEPORT=yCONFIG_GAMEPORT_NS558=yCONFIG_GAMEPORT_L4=yCONFIG_GAMEPORT_EMU10K1=yCONFIG_GAMEPORT_FM801=y
#
# Character devices
#CONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#CONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=4CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not setCONFIG_SERIAL_8250_SHARE_IRQ=yCONFIG_SERIAL_8250_DETECT_IRQ=yCONFIG_SERIAL_8250_RSA=y
# CONFIG_SERIAL_8250_MCA is not set
#
# Non-8250 serial port support
#CONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_SERIAL_JSM=yCONFIG_UNIX98_PTYS=yCONFIG_DEVPTS_MULTIPLE_INSTANCES=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256CONFIG_PRINTER=yCONFIG_LP_CONSOLE=yCONFIG_PPDEV=yCONFIG_HVC_DRIVER=y
# CONFIG_VIRTIO_CONSOLE is not setCONFIG_IPMI_HANDLER=yCONFIG_IPMI_PANIC_EVENT=yCONFIG_IPMI_PANIC_STRING=y
# CONFIG_IPMI_DEVICE_INTERFACE is not setCONFIG_IPMI_SI=yCONFIG_IPMI_WATCHDOG=y
# CONFIG_IPMI_POWEROFF is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not setCONFIG_R3964=yCONFIG_APPLICOM=y
# CONFIG_SONYPI is not setCONFIG_MWAVE=y
CONFIG_PC8736x_GPIO=yCONFIG_NSC_GPIO=yCONFIG_CS5535_GPIO=y
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not setCONFIG_DEVPORT=yCONFIG_I2C=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_CHARDEV=yCONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#CONFIG_I2C_ALI1535=yCONFIG_I2C_ALI1563=yCONFIG_I2C_ALI15X3=y
# CONFIG_I2C_AMD756 is not setCONFIG_I2C_AMD8111=yCONFIG_I2C_I801=yCONFIG_I2C_ISCH=y
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not setCONFIG_I2C_SIS5595=yCONFIG_I2C_SIS630=yCONFIG_I2C_SIS96X=yCONFIG_I2C_VIA=yCONFIG_I2C_VIAPRO=y
#
# I2C system bus drivers (mostly embedded / system-on-chip) #CONFIG_I2C_GPIO=yCONFIG_I2C_OCORES=yCONFIG_I2C_SIMTEC=y
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not setCONFIG_I2C_TAOS_EVM=yCONFIG_I2C_TINY_USB=y
#
# Graphics adapter I2C/DDC channel drivers
#
# CONFIG_I2C_VOODOO3 is not set
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_PCA_PLATFORM=y
# CONFIG_SCx200_ACB is not set
#
# Miscellaneous I2C Chip support
#CONFIG_DS1682=yCONFIG_SENSORS_PCF8574=yCONFIG_PCF8575=yCONFIG_SENSORS_PCF8591=yCONFIG_SENSORS_MAX6875=y
# CONFIG_SENSORS_TSL2550 is not setCONFIG_I2C_DEBUG_CORE=y
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not setCONFIG_SPI=yCONFIG_SPI_DEBUG=yCONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#CONFIG_SPI_BITBANG=yCONFIG_SPI_BUTTERFLY=y
# CONFIG_SPI_GPIO is not setCONFIG_SPI_LM70_LLP=y
#
# SPI Protocol Masters
#CONFIG_SPI_SPIDEV=yCONFIG_SPI_TLE62X0=yCONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=yCONFIG_GPIOLIB=yCONFIG_DEBUG_GPIO=y
# CONFIG_GPIO_SYSFS is not set
#
# Memory mapped GPIO expanders:
#
#
# I2C GPIO expanders:
#CONFIG_GPIO_MAX732X=yCONFIG_GPIO_PCA953X=y
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TWL4030 is not set
#
# PCI GPIO expanders:
#CONFIG_GPIO_BT8XX=y
#
# SPI GPIO expanders:
#CONFIG_GPIO_MAX7301=yCONFIG_GPIO_MCP23S08=yCONFIG_W1=yCONFIG_W1_CON=y
#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_MATROX is not set
# CONFIG_W1_MASTER_DS2490 is not set
# CONFIG_W1_MASTER_DS2482 is not set
# CONFIG_W1_MASTER_GPIO is not set
#
# 1-wire Slaves
#
# CONFIG_W1_SLAVE_THERM is not set
# CONFIG_W1_SLAVE_SMEM is not set
# CONFIG_W1_SLAVE_DS2431 is not setCONFIG_W1_SLAVE_DS2433=yCONFIG_W1_SLAVE_DS2433_CRC=yCONFIG_W1_SLAVE_DS2760=yCONFIG_W1_SLAVE_BQ27000=y
# CONFIG_POWER_SUPPLY is not setCONFIG_HWMON=yCONFIG_HWMON_VID=yCONFIG_SENSORS_ABITUGURU=yCONFIG_SENSORS_ABITUGURU3=y
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not setCONFIG_SENSORS_ADCXX=yCONFIG_SENSORS_ADM1021=yCONFIG_SENSORS_ADM1025=yCONFIG_SENSORS_ADM1026=yCONFIG_SENSORS_ADM1029=yCONFIG_SENSORS_ADM1031=yCONFIG_SENSORS_ADM9240=yCONFIG_SENSORS_ADT7462=y
# CONFIG_SENSORS_ADT7470 is not setCONFIG_SENSORS_ADT7473=yCONFIG_SENSORS_ADT7475=yCONFIG_SENSORS_K8TEMP=yCONFIG_SENSORS_ASB100=y
# CONFIG_SENSORS_ATXP1 is not setCONFIG_SENSORS_DS1621=yCONFIG_SENSORS_I5K_AMB=yCONFIG_SENSORS_F71805F=y
# CONFIG_SENSORS_F71882FG is not setCONFIG_SENSORS_F75375S=yCONFIG_SENSORS_FSCHER=yCONFIG_SENSORS_FSCPOS=yCONFIG_SENSORS_FSCHMD=yCONFIG_SENSORS_GL518SM=yCONFIG_SENSORS_GL520SM=y
# CONFIG_SENSORS_CORETEMP is not setCONFIG_SENSORS_IBMAEM=yCONFIG_SENSORS_IBMPEX=yCONFIG_SENSORS_IT87=y
# CONFIG_SENSORS_LM63 is not setCONFIG_SENSORS_LM70=yCONFIG_SENSORS_LM75=y
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not setCONFIG_SENSORS_LM80=y
# CONFIG_SENSORS_LM83 is not setCONFIG_SENSORS_LM85=y
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4245 is not setCONFIG_SENSORS_MAX1111=y
# CONFIG_SENSORS_MAX1619 is not setCONFIG_SENSORS_MAX6650=y
# CONFIG_SENSORS_PC87360 is not setCONFIG_SENSORS_PC87427=yCONFIG_SENSORS_SIS5595=yCONFIG_SENSORS_DME1737=yCONFIG_SENSORS_SMSC47M1=yCONFIG_SENSORS_SMSC47M192=yCONFIG_SENSORS_SMSC47B397=yCONFIG_SENSORS_ADS7828=yCONFIG_SENSORS_THMC50=y
# CONFIG_SENSORS_VIA686A is not setCONFIG_SENSORS_VT1211=yCONFIG_SENSORS_VT8231=yCONFIG_SENSORS_W83781D=yCONFIG_SENSORS_W83791D=y
# CONFIG_SENSORS_W83792D is not setCONFIG_SENSORS_W83793=yCONFIG_SENSORS_W83L785TS=y
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not setCONFIG_SENSORS_W83627EHF=yCONFIG_SENSORS_HDAPS=yCONFIG_SENSORS_APPLESMC=yCONFIG_HWMON_DEBUG_CHIP=yCONFIG_THERMAL=yCONFIG_THERMAL_HWMON=yCONFIG_WATCHDOG=yCONFIG_WATCHDOG_NOWAYOUT=y
#
# Watchdog Device Drivers
#CONFIG_SOFT_WATCHDOG=yCONFIG_ACQUIRE_WDT=yCONFIG_ADVANTECH_WDT=yCONFIG_ALIM1535_WDT=yCONFIG_ALIM7101_WDT=y
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not setCONFIG_IB700_WDT=yCONFIG_IBMASR=y
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not setCONFIG_ITCO_WDT=yCONFIG_ITCO_VENDOR_SUPPORT=y
# CONFIG_IT8712F_WDT is not setCONFIG_IT87_WDT=yCONFIG_HP_WATCHDOG=yCONFIG_SC1200_WDT=y
# CONFIG_PC87413_WDT is not setCONFIG_RDC321X_WDT=yCONFIG_60XX_WDT=yCONFIG_SBC8360_WDT=y
# CONFIG_SBC7240_WDT is not setCONFIG_CPU5_WDT=y
# CONFIG_SMSC_SCH311X_WDT is not setCONFIG_SMSC37B787_WDT=yCONFIG_W83627HF_WDT=y
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83697UG_WDT is not setCONFIG_W83877F_WDT=yCONFIG_W83977F_WDT=yCONFIG_MACHZ_WDT=yCONFIG_SBC_EPX_C3_WATCHDOG=y
#
# PCI-based Watchdog Cards
#CONFIG_PCIPCWATCHDOG=y
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#CONFIG_USBPCWATCHDOG=yCONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#CONFIG_SSB=yCONFIG_SSB_SPROM=yCONFIG_SSB_PCIHOST_POSSIBLE=yCONFIG_SSB_PCIHOST=y
# CONFIG_SSB_B43_PCI_BRIDGE is not setCONFIG_SSB_SILENT=yCONFIG_SSB_DRIVER_PCICORE_POSSIBLE=yCONFIG_SSB_DRIVER_PCICORE=y
#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not setCONFIG_MFD_SM501=y
# CONFIG_MFD_SM501_GPIO is not set
# CONFIG_HTC_PASIC3 is not setCONFIG_TPS65010=yCONFIG_TWL4030_CORE=y
# CONFIG_MFD_TMIO is not setCONFIG_PMIC_DA903X=y
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM8350_I2C is not setCONFIG_MFD_PCF50633=yCONFIG_PCF50633_ADC=yCONFIG_PCF50633_GPIO=yCONFIG_REGULATOR=yCONFIG_REGULATOR_DEBUG=y
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not setCONFIG_REGULATOR_BQ24022=yCONFIG_REGULATOR_DA903X=yCONFIG_REGULATOR_PCF50633=y
#
# Multimedia devices
#
#
# Multimedia core support
#CONFIG_VIDEO_DEV=yCONFIG_VIDEO_V4L2_COMMON=y
# CONFIG_VIDEO_ALLOW_V4L1 is not set
# CONFIG_VIDEO_V4L1_COMPAT is not setCONFIG_DVB_CORE=yCONFIG_VIDEO_MEDIA=y
#
# Multimedia drivers
#CONFIG_VIDEO_SAA7146=yCONFIG_VIDEO_SAA7146_VV=yCONFIG_MEDIA_TUNER=yCONFIG_MEDIA_TUNER_CUSTOMIZE=yCONFIG_MEDIA_TUNER_SIMPLE=yCONFIG_MEDIA_TUNER_TDA8290=yCONFIG_MEDIA_TUNER_TDA827X=yCONFIG_MEDIA_TUNER_TDA18271=yCONFIG_MEDIA_TUNER_TDA9887=y
# CONFIG_MEDIA_TUNER_TEA5761 is not setCONFIG_MEDIA_TUNER_TEA5767=y
# CONFIG_MEDIA_TUNER_MT20XX is not setCONFIG_MEDIA_TUNER_MT2060=yCONFIG_MEDIA_TUNER_MT2266=yCONFIG_MEDIA_TUNER_MT2131=yCONFIG_MEDIA_TUNER_QT1010=y
# CONFIG_MEDIA_TUNER_XC2028 is not setCONFIG_MEDIA_TUNER_XC5000=y
# CONFIG_MEDIA_TUNER_MXL5005S is not setCONFIG_MEDIA_TUNER_MXL5007T=yCONFIG_VIDEO_V4L2=yCONFIG_VIDEOBUF_GEN=yCONFIG_VIDEOBUF_DMA_SG=yCONFIG_VIDEOBUF_VMALLOC=yCONFIG_VIDEO_IR=yCONFIG_VIDEO_TVEEPROM=yCONFIG_VIDEO_TUNER=yCONFIG_VIDEO_CAPTURE_DRIVERS=yCONFIG_VIDEO_ADV_DEBUG=yCONFIG_VIDEO_FIXED_MINOR_RANGES=yCONFIG_VIDEO_HELPER_CHIPS_AUTO=yCONFIG_VIDEO_IR_I2C=yCONFIG_VIDEO_MSP3400=yCONFIG_VIDEO_CS5345=yCONFIG_VIDEO_CS53L32A=yCONFIG_VIDEO_M52790=yCONFIG_VIDEO_WM8775=yCONFIG_VIDEO_WM8739=yCONFIG_VIDEO_VP27SMPX=yCONFIG_VIDEO_SAA711X=yCONFIG_VIDEO_SAA717X=yCONFIG_VIDEO_TVP5150=yCONFIG_VIDEO_CX25840=yCONFIG_VIDEO_CX2341X=yCONFIG_VIDEO_SAA7127=yCONFIG_VIDEO_UPD64031A=yCONFIG_VIDEO_UPD64083=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not setCONFIG_VIDEO_SAA7134=y
# CONFIG_VIDEO_SAA7134_DVB is not setCONFIG_VIDEO_HEXIUM_ORION=y
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_CX23885 is not setCONFIG_VIDEO_AU0828=yCONFIG_VIDEO_IVTV=yCONFIG_VIDEO_FB_IVTV=yCONFIG_VIDEO_CX18=y
# CONFIG_VIDEO_CAFE_CCIC is not set
# CONFIG_SOC_CAMERA is not setCONFIG_V4L_USB_DRIVERS=y
# CONFIG_USB_VIDEO_CLASS is not set
# CONFIG_USB_GSPCA is not setCONFIG_VIDEO_PVRUSB2=y
# CONFIG_VIDEO_PVRUSB2_SYSFS is not set
# CONFIG_VIDEO_PVRUSB2_DVB is not setCONFIG_VIDEO_EM28XX=y
# CONFIG_VIDEO_EM28XX_DVB is not setCONFIG_VIDEO_USBVISION=y
# CONFIG_USB_ET61X251 is not setCONFIG_USB_SN9C102=y
# CONFIG_USB_ZC0301 is not setCONFIG_USB_ZR364XX=yCONFIG_USB_STKWEBCAM=y
# CONFIG_USB_S2255 is not set
# CONFIG_RADIO_ADAPTERS is not set
# CONFIG_DVB_DYNAMIC_MINORS is not setCONFIG_DVB_CAPTURE_DRIVERS=y
#
# Supported SAA7146 based PCI Adapters
#
# CONFIG_TTPCI_EEPROM is not set
# CONFIG_DVB_AV7110 is not set
# CONFIG_DVB_BUDGET_CORE is not set
#
# Supported USB Adapters
#CONFIG_DVB_USB=yCONFIG_DVB_USB_DEBUG=y
# CONFIG_DVB_USB_A800 is not setCONFIG_DVB_USB_DIBUSB_MB=y
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
# CONFIG_DVB_USB_DIBUSB_MC is not set
# CONFIG_DVB_USB_DIB0700 is not setCONFIG_DVB_USB_UMT_010=yCONFIG_DVB_USB_CXUSB=y
# CONFIG_DVB_USB_M920X is not setCONFIG_DVB_USB_GL861=y
# CONFIG_DVB_USB_AU6610 is not set
# CONFIG_DVB_USB_DIGITV is not setCONFIG_DVB_USB_VP7045=yCONFIG_DVB_USB_VP702X=y
# CONFIG_DVB_USB_GP8PSK is not set
# CONFIG_DVB_USB_NOVA_T_USB2 is not setCONFIG_DVB_USB_TTUSB2=yCONFIG_DVB_USB_DTT200U=yCONFIG_DVB_USB_OPERA1=y
# CONFIG_DVB_USB_AF9005 is not set
# CONFIG_DVB_USB_DW2102 is not setCONFIG_DVB_USB_CINERGY_T2=y
# CONFIG_DVB_USB_ANYSEE is not setCONFIG_DVB_USB_DTV5100=yCONFIG_DVB_USB_AF9015=y
# CONFIG_DVB_TTUSB_BUDGET is not setCONFIG_DVB_TTUSB_DEC=yCONFIG_DVB_SIANO_SMS1XXX=y
# CONFIG_DVB_SIANO_SMS1XXX_SMS_IDS is not set
#
# Supported FlexCopII (B2C2) Adapters
#CONFIG_DVB_B2C2_FLEXCOP=yCONFIG_DVB_B2C2_FLEXCOP_PCI=y
# CONFIG_DVB_B2C2_FLEXCOP_USB is not setCONFIG_DVB_B2C2_FLEXCOP_DEBUG=y
#
# Supported BT878 Adapters
#
#
# Supported Pluto2 Adapters
#CONFIG_DVB_PLUTO2=y
#
# Supported SDMC DM1105 Adapters
#
# CONFIG_DVB_DM1105 is not set
#
# Supported FireWire (IEEE 1394) Adapters
#
# CONFIG_DVB_FIREDTV is not set
#
# Supported DVB Frontends
#
#
# Customise DVB Frontends
#CONFIG_DVB_FE_CUSTOMISE=y
#
# Multistandard (satellite) frontends
#
# CONFIG_DVB_STB0899 is not set
# CONFIG_DVB_STB6100 is not set
#
# DVB-S (satellite) frontends
#CONFIG_DVB_CX24110=y
# CONFIG_DVB_CX24123 is not set
# CONFIG_DVB_MT312 is not set
# CONFIG_DVB_S5H1420 is not setCONFIG_DVB_STV0288=yCONFIG_DVB_STB6000=yCONFIG_DVB_STV0299=y
# CONFIG_DVB_TDA8083 is not set
# CONFIG_DVB_TDA10086 is not setCONFIG_DVB_TDA8261=y
# CONFIG_DVB_VES1X93 is not setCONFIG_DVB_TUNER_ITD1000=yCONFIG_DVB_TUNER_CX24113=y
# CONFIG_DVB_TDA826X is not setCONFIG_DVB_TUA6100=yCONFIG_DVB_CX24116=yCONFIG_DVB_SI21XX=y
#
# DVB-T (terrestrial) frontends
#
# CONFIG_DVB_SP8870 is not setCONFIG_DVB_SP887X=yCONFIG_DVB_CX22700=y
# CONFIG_DVB_CX22702 is not set
# CONFIG_DVB_DRX397XD is not setCONFIG_DVB_L64781=yCONFIG_DVB_TDA1004X=y
# CONFIG_DVB_NXT6000 is not set
# CONFIG_DVB_MT352 is not setCONFIG_DVB_ZL10353=yCONFIG_DVB_DIB3000MB=yCONFIG_DVB_DIB3000MC=yCONFIG_DVB_DIB7000M=yCONFIG_DVB_DIB7000P=yCONFIG_DVB_TDA10048=y
#
# DVB-C (cable) frontends
#CONFIG_DVB_VES1820=y
# CONFIG_DVB_TDA10021 is not setCONFIG_DVB_TDA10023=yCONFIG_DVB_STV0297=y
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #
# CONFIG_DVB_NXT200X is not set
# CONFIG_DVB_OR51211 is not set
# CONFIG_DVB_OR51132 is not set
# CONFIG_DVB_BCM3510 is not set CONFIG_DVB_LGDT330X=yCONFIG_DVB_LGDT3304=yCONFIG_DVB_S5H1409=yCONFIG_DVB_AU8522=yCONFIG_DVB_S5H1411=y
#
# ISDB-T (terrestrial) frontends
#
# CONFIG_DVB_S921 is not set
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=y
# CONFIG_DVB_TUNER_DIB0070 is not set
#
# SEC control devices for DVB-S
#
# CONFIG_DVB_LNBP21 is not setCONFIG_DVB_ISL6405=yCONFIG_DVB_ISL6421=yCONFIG_DVB_LGS8GL5=y
#
# Tools to develop new frontends
#CONFIG_DVB_DUMMY_FE=yCONFIG_DVB_AF9013=yCONFIG_DAB=yCONFIG_USB_DABUSB=y
#
# Graphics support
#
# CONFIG_AGP is not setCONFIG_DRM=yCONFIG_DRM_TDFX=yCONFIG_DRM_R128=y
# CONFIG_DRM_RADEON is not setCONFIG_DRM_MGA=yCONFIG_DRM_VIA=yCONFIG_DRM_SAVAGE=yCONFIG_VGASTATE=yCONFIG_VIDEO_OUTPUT_CONTROL=yCONFIG_FB=yCONFIG_FIRMWARE_EDID=yCONFIG_FB_DDC=yCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not setCONFIG_FB_SYS_FILLRECT=yCONFIG_FB_SYS_COPYAREA=yCONFIG_FB_SYS_IMAGEBLIT=yCONFIG_FB_FOREIGN_ENDIAN=y
# CONFIG_FB_BOTH_ENDIAN is not setCONFIG_FB_BIG_ENDIAN=y
# CONFIG_FB_LITTLE_ENDIAN is not setCONFIG_FB_SYS_FOPS=yCONFIG_FB_DEFERRED_IO=yCONFIG_FB_HECUBA=yCONFIG_FB_SVGALIB=y
# CONFIG_FB_MACMODES is not setCONFIG_FB_BACKLIGHT=yCONFIG_FB_MODE_HELPERS=yCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not setCONFIG_FB_PM2=y
# CONFIG_FB_PM2_FIFO_DISCONNECT is not setCONFIG_FB_CYBER2000=y
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not setCONFIG_FB_IMSTT=y
# CONFIG_FB_VGA16 is not setCONFIG_FB_UVESA=y
# CONFIG_FB_VESA is not setCONFIG_FB_N411=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not setCONFIG_FB_RIVA=yCONFIG_FB_RIVA_I2C=yCONFIG_FB_RIVA_DEBUG=yCONFIG_FB_RIVA_BACKLIGHT=yCONFIG_FB_LE80578=y
# CONFIG_FB_CARILLO_RANCH is not setCONFIG_FB_MATROX=yCONFIG_FB_MATROX_MILLENIUM=yCONFIG_FB_MATROX_MYSTIQUE=yCONFIG_FB_MATROX_G=yCONFIG_FB_MATROX_I2C=yCONFIG_FB_MATROX_MAVEN=yCONFIG_FB_MATROX_MULTIHEAD=y
# CONFIG_FB_RADEON is not setCONFIG_FB_ATY128=yCONFIG_FB_ATY128_BACKLIGHT=y
# CONFIG_FB_ATY is not setCONFIG_FB_S3=yCONFIG_FB_SAVAGE=yCONFIG_FB_SAVAGE_I2C=yCONFIG_FB_SAVAGE_ACCEL=yCONFIG_FB_SIS=yCONFIG_FB_SIS_300=yCONFIG_FB_SIS_315=yCONFIG_FB_VIA=yCONFIG_FB_NEOMAGIC=yCONFIG_FB_KYRO=yCONFIG_FB_3DFX=y
# CONFIG_FB_3DFX_ACCEL is not setCONFIG_FB_VOODOO1=yCONFIG_FB_VT8623=y
# CONFIG_FB_CYBLA is not setCONFIG_FB_TRIDENT=y
# CONFIG_FB_TRIDENT_ACCEL is not setCONFIG_FB_ARK=yCONFIG_FB_PM3=yCONFIG_FB_CARMINE=y
# CONFIG_FB_CARMINE_DRAM_EVAL is not setCONFIG_CARMINE_DRAM_CUSTOM=yCONFIG_FB_GEODE=yCONFIG_FB_GEODE_LX=yCONFIG_FB_GEODE_GX=yCONFIG_FB_GEODE_GX1=yCONFIG_FB_SM501=y
# CONFIG_FB_VIRTUAL is not setCONFIG_FB_METRONOME=yCONFIG_FB_MB862XX=y
# CONFIG_FB_MB862XX_PCI_GDC is not setCONFIG_BACKLIGHT_LCD_SUPPORT=yCONFIG_LCD_CLASS_DEVICE=yCONFIG_LCD_LTV350QV=yCONFIG_LCD_ILI9320=y
# CONFIG_LCD_TDO24M is not setCONFIG_LCD_VGG2432A4=yCONFIG_LCD_PLATFORM=yCONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not setCONFIG_BACKLIGHT_PROGEAR=yCONFIG_BACKLIGHT_CARILLO_RANCH=yCONFIG_BACKLIGHT_DA903X=y
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA is not set
#
# Display device support
#CONFIG_DISPLAY_SUPPORT=y
#
# Display hardware drivers
#
#
# Console display driver support
#CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not setCONFIG_DUMMY_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE is not set
CONFIG_FONT_8x16=yCONFIG_LOGO=yCONFIG_LOGO_LINUX_MONO=y
# CONFIG_LOGO_LINUX_VGA16 is not set
# CONFIG_LOGO_LINUX_CLUT224 is not setCONFIG_SOUND=y
# CONFIG_SOUND_OSS_CORE is not set
# CONFIG_SND is not set
# CONFIG_SOUND_PRIME is not set
# CONFIG_HID_SUPPORT is not setCONFIG_USB_SUPPORT=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=yCONFIG_USB_ARCH_HAS_EHCI=yCONFIG_USB=yCONFIG_USB_DEBUG=y
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_DEVICE_CLASS is not setCONFIG_USB_DYNAMIC_MINORS=yCONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not setCONFIG_USB_OTG_WHITELIST=yCONFIG_USB_OTG_BLACKLIST_HUB=y
# CONFIG_USB_MON is not setCONFIG_USB_WUSB=yCONFIG_USB_WUSB_CBAF=y
# CONFIG_USB_WUSB_CBAF_DEBUG is not set
#
# USB Host Controller Drivers
#CONFIG_USB_C67X00_HCD=yCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_EHCI_TT_NEWSCHED=yCONFIG_USB_OXU210HP_HCD=yCONFIG_USB_ISP116X_HCD=y
# CONFIG_USB_ISP1760_HCD is not setCONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not setCONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_UHCI_HCD=yCONFIG_USB_U132_HCD=y
# CONFIG_USB_SL811_HCD is not setCONFIG_USB_R8A66597_HCD=y
# CONFIG_USB_WHCI_HCD is not setCONFIG_USB_HWA_HCD=y
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not setCONFIG_USB_PRINTER=y
# CONFIG_USB_WDM is not setCONFIG_USB_TMC=y
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed; #
#
# see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=y CONFIG_USB_STORAGE_DEBUG=y # CONFIG_USB_STORAGE_DATAFAB is not set CONFIG_USB_STORAGE_FREECOM=y CONFIG_USB_STORAGE_ISD200=y CONFIG_USB_STORAGE_USBAT=y CONFIG_USB_STORAGE_SDDR09=y # CONFIG_USB_STORAGE_SDDR55 is not set CONFIG_USB_STORAGE_JUMPSHOT=y CONFIG_USB_STORAGE_ALAUDA=y # CONFIG_USB_STORAGE_ONETOUCH is not set CONFIG_USB_STORAGE_KARMA=y CONFIG_USB_STORAGE_CYPRESS_ATACB=y # CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
#
# USB port drivers
#CONFIG_USB_USS720=yCONFIG_USB_SERIAL=yCONFIG_USB_SERIAL_CONSOLE=yCONFIG_USB_EZUSB=y
# CONFIG_USB_SERIAL_GENERIC is not setCONFIG_USB_SERIAL_AIRCABLE=yCONFIG_USB_SERIAL_ARK3116=yCONFIG_USB_SERIAL_BELKIN=yCONFIG_USB_SERIAL_CH341=yCONFIG_USB_SERIAL_WHITEHEAT=yCONFIG_USB_SERIAL_DIGI_ACCELEPORT=yCONFIG_USB_SERIAL_CP2101=yCONFIG_USB_SERIAL_CYPRESS_M8=yCONFIG_USB_SERIAL_EMPEG=yCONFIG_USB_SERIAL_FTDI_SIO=yCONFIG_USB_SERIAL_FUNSOFT=yCONFIG_USB_SERIAL_VISOR=yCONFIG_USB_SERIAL_IPAQ=y
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not setCONFIG_USB_SERIAL_EDGEPORT_TI=yCONFIG_USB_SERIAL_GARMIN=y
# CONFIG_USB_SERIAL_IPW is not setCONFIG_USB_SERIAL_IUU=yCONFIG_USB_SERIAL_KEYSPAN_PDA=yCONFIG_USB_SERIAL_KEYSPAN=yCONFIG_USB_SERIAL_KEYSPAN_MPR=yCONFIG_USB_SERIAL_KEYSPAN_USA28=y
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not setCONFIG_USB_SERIAL_KEYSPAN_USA28XA=yCONFIG_USB_SERIAL_KEYSPAN_USA28XB=yCONFIG_USB_SERIAL_KEYSPAN_USA19=y
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not setCONFIG_USB_SERIAL_KEYSPAN_USA19QW=yCONFIG_USB_SERIAL_KEYSPAN_USA19QI=yCONFIG_USB_SERIAL_KEYSPAN_USA49W=yCONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
# CONFIG_USB_SERIAL_KLSI is not setCONFIG_USB_SERIAL_KOBIL_SCT=yCONFIG_USB_SERIAL_MCT_U232=y
# CONFIG_USB_SERIAL_MOS7720 is not setCONFIG_USB_SERIAL_MOS7840=yCONFIG_USB_SERIAL_MOTOROLA=yCONFIG_USB_SERIAL_NAVMAN=y
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_OTI6858 is not setCONFIG_USB_SERIAL_SPCP8X5=yCONFIG_USB_SERIAL_HP4X=yCONFIG_USB_SERIAL_SAFE=yCONFIG_USB_SERIAL_SAFE_PADDED=y
# CONFIG_USB_SERIAL_SIEMENS_MPI is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not setCONFIG_USB_SERIAL_TI=yCONFIG_USB_SERIAL_CYBERJACK=y
# CONFIG_USB_SERIAL_XIRCOM is not setCONFIG_USB_SERIAL_OPTION=y
# CONFIG_USB_SERIAL_OMNINET is not setCONFIG_USB_SERIAL_OPTICON=yCONFIG_USB_SERIAL_DEBUG=y
#
# USB Miscellaneous drivers
#CONFIG_USB_EMI62=yCONFIG_USB_EMI26=yCONFIG_USB_ADUTUX=y
# CONFIG_USB_SEVSEG is not setCONFIG_USB_RIO500=yCONFIG_USB_LEGOTOWER=y
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not setCONFIG_USB_CYPRESS_CY7C63=y
# CONFIG_USB_CYTHERM is not setCONFIG_USB_PHIDGET=yCONFIG_USB_PHIDGETKIT=yCONFIG_USB_PHIDGETMOTORCONTROL=yCONFIG_USB_PHIDGETSERVO=yCONFIG_USB_IDMOUSE=yCONFIG_USB_FTDI_ELAN=yCONFIG_USB_APPLEDISPLAY=yCONFIG_USB_SISUSBVGA=yCONFIG_USB_SISUSBVGA_CON=yCONFIG_USB_LD=yCONFIG_USB_TRANCEVIBRATOR=yCONFIG_USB_IOWARRIOR=yCONFIG_USB_ISIGHTFW=y
# CONFIG_USB_VST is not set
# CONFIG_USB_ATM is not set
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#CONFIG_USB_OTG_UTILS=yCONFIG_USB_GPIO_VBUS=yCONFIG_TWL4030_USB=yCONFIG_UWB=yCONFIG_UWB_HWA=y
# CONFIG_UWB_WHCI is not setCONFIG_UWB_WLP=y
# CONFIG_UWB_I1480U is not setCONFIG_MMC=yCONFIG_MMC_DEBUG=yCONFIG_MMC_UNSAFE_RESUME=y
#
# MMC/SD/SDIO Card Drivers
#CONFIG_MMC_BLOCK=yCONFIG_MMC_BLOCK_BOUNCE=yCONFIG_SDIO_UART=yCONFIG_MMC_TEST=y
#
# MMC/SD/SDIO Host Controller Drivers
#CONFIG_MMC_SDHCI=yCONFIG_MMC_SDHCI_PCI=y
# CONFIG_MMC_RICOH_MMC is not set
# CONFIG_MMC_WBSD is not setCONFIG_MMC_TIFM_SD=yCONFIG_MEMSTICK=y
# CONFIG_MEMSTICK_DEBUG is not set
#
# MemoryStick drivers
#CONFIG_MEMSTICK_UNSAFE_RESUME=yCONFIG_MSPRO_BLOCK=y
#
# MemoryStick Host Controller Drivers
#
# CONFIG_MEMSTICK_TIFM_MS is not setCONFIG_MEMSTICK_JMICRON_38X=yCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
#
# LED drivers
#
# CONFIG_LEDS_ALIX2 is not setCONFIG_LEDS_PCA9532=yCONFIG_LEDS_GPIO=yCONFIG_LEDS_CLEVO_MAIL=yCONFIG_LEDS_PCA955X=yCONFIG_LEDS_DA903X=y
#
# LED Triggers
#
# CONFIG_LEDS_TRIGGERS is not setCONFIG_ACCESSIBILITY=yCONFIG_A11Y_BRAILLE_CONSOLE=y
# CONFIG_INFINIBAND is not setCONFIG_EDAC=y
#
# Reporting subsystems
#CONFIG_EDAC_DEBUG=yCONFIG_EDAC_MM_EDAC=y
# CONFIG_EDAC_AMD76X is not set
# CONFIG_EDAC_E7XXX is not setCONFIG_EDAC_E752X=yCONFIG_EDAC_I82875P=y
# CONFIG_EDAC_I82975X is not setCONFIG_EDAC_I3000=yCONFIG_EDAC_X38=y
# CONFIG_EDAC_I5400 is not set
# CONFIG_EDAC_I82860 is not setCONFIG_EDAC_R82600=yCONFIG_EDAC_I5000=yCONFIG_EDAC_I5100=yCONFIG_RTC_LIB=yCONFIG_RTC_CLASS=yCONFIG_RTC_HCTOSYS=yCONFIG_RTC_HCTOSYS_DEVICE="rtc0"CONFIG_RTC_DEBUG=y
#
# RTC interfaces
#
# CONFIG_RTC_INTF_SYSFS is not setCONFIG_RTC_INTF_PROC=yCONFIG_RTC_INTF_DEV=yCONFIG_RTC_INTF_DEV_UIE_EMUL=yCONFIG_RTC_DRV_TEST=y
#
# I2C RTC drivers
#CONFIG_RTC_DRV_DS1307=yCONFIG_RTC_DRV_DS1374=y
# CONFIG_RTC_DRV_DS1672 is not setCONFIG_RTC_DRV_MAX6900=yCONFIG_RTC_DRV_RS5C372=y
# CONFIG_RTC_DRV_ISL1208 is not setCONFIG_RTC_DRV_X1205=yCONFIG_RTC_DRV_PCF8563=yCONFIG_RTC_DRV_PCF8583=yCONFIG_RTC_DRV_M41T80=yCONFIG_RTC_DRV_M41T80_WDT=yCONFIG_RTC_DRV_TWL4030=yCONFIG_RTC_DRV_S35390A=yCONFIG_RTC_DRV_FM3130=yCONFIG_RTC_DRV_RX8581=y
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T94 is not setCONFIG_RTC_DRV_DS1305=yCONFIG_RTC_DRV_DS1390=yCONFIG_RTC_DRV_MAX6902=yCONFIG_RTC_DRV_R9701=yCONFIG_RTC_DRV_RS5C348=yCONFIG_RTC_DRV_DS3234=y
#
# Platform RTC drivers
#CONFIG_RTC_DRV_CMOS=yCONFIG_RTC_DRV_DS1286=yCONFIG_RTC_DRV_DS1511=yCONFIG_RTC_DRV_DS1553=yCONFIG_RTC_DRV_DS1742=yCONFIG_RTC_DRV_STK17TA8=yCONFIG_RTC_DRV_M48T86=yCONFIG_RTC_DRV_M48T35=yCONFIG_RTC_DRV_M48T59=yCONFIG_RTC_DRV_BQ4802=yCONFIG_RTC_DRV_V3020=yCONFIG_RTC_DRV_PCF50633=y
#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not setCONFIG_UIO=yCONFIG_UIO_CIF=y
# CONFIG_UIO_PDRV is not set
# CONFIG_UIO_PDRV_GENIRQ is not set
# CONFIG_UIO_SMX is not setCONFIG_UIO_SERCOS3=y
# CONFIG_STAGING is not setCONFIG_X86_PLATFORM_DEVICES=y
#
# Firmware Drivers
#CONFIG_EDD=yCONFIG_EDD_OFF=yCONFIG_FIRMWARE_MEMMAP=yCONFIG_DELL_RBU=yCONFIG_DCDBAS=yCONFIG_DMIID=y
# CONFIG_ISCSI_IBFT_FIND is not set
#
# File systems
#CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not setCONFIG_EXT2_FS_XIP=yCONFIG_EXT3_FS=yCONFIG_EXT3_FS_XATTR=yCONFIG_EXT3_FS_POSIX_ACL=yCONFIG_EXT3_FS_SECURITY=yCONFIG_EXT4_FS=y
# CONFIG_EXT4DEV_COMPAT is not set
# CONFIG_EXT4_FS_XATTR is not setCONFIG_FS_XIP=yCONFIG_JBD=yCONFIG_JBD_DEBUG=yCONFIG_JBD2=yCONFIG_JBD2_DEBUG=yCONFIG_FS_MBCACHE=yCONFIG_REISERFS_FS=yCONFIG_REISERFS_CHECK=yCONFIG_REISERFS_PROC_INFO=y
# CONFIG_REISERFS_FS_XATTR is not setCONFIG_JFS_FS=y
# CONFIG_JFS_POSIX_ACL is not setCONFIG_JFS_SECURITY=yCONFIG_JFS_DEBUG=y
# CONFIG_JFS_STATISTICS is not setCONFIG_FS_POSIX_ACL=yCONFIG_FILE_LOCKING=yCONFIG_XFS_FS=yCONFIG_XFS_QUOTA=yCONFIG_XFS_POSIX_ACL=yCONFIG_XFS_RT=y
# CONFIG_XFS_DEBUG is not set
# CONFIG_GFS2_FS is not setCONFIG_OCFS2_FS=yCONFIG_OCFS2_FS_O2CB=y
# CONFIG_OCFS2_FS_USERSPACE_CLUSTER is not set
# CONFIG_OCFS2_FS_STATS is not setCONFIG_OCFS2_DEBUG_MASKLOG=yCONFIG_OCFS2_DEBUG_FS=yCONFIG_OCFS2_FS_POSIX_ACL=yCONFIG_BTRFS_FS=yCONFIG_BTRFS_FS_POSIX_ACL=yCONFIG_DNOTIFY=yCONFIG_INOTIFY=y
# CONFIG_INOTIFY_USER is not setCONFIG_QUOTA=yCONFIG_QUOTA_NETLINK_INTERFACE=yCONFIG_PRINT_QUOTA_WARNING=yCONFIG_QUOTA_TREE=yCONFIG_QFMT_V1=y
# CONFIG_QFMT_V2 is not setCONFIG_QUOTACTL=yCONFIG_AUTOFS_FS=y
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#CONFIG_ISO9660_FS=yCONFIG_JOLIET=yCONFIG_ZISOFS=yCONFIG_UDF_FS=yCONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#CONFIG_FAT_FS=yCONFIG_MSDOS_FS=yCONFIG_VFAT_FS=yCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#CONFIG_PROC_FS=yCONFIG_PROC_KCORE=y
# CONFIG_PROC_SYSCTL is not setCONFIG_PROC_PAGE_MONITOR=yCONFIG_SYSFS=yCONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not setCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=yCONFIG_CONFIGFS_FS=yCONFIG_MISC_FILESYSTEMS=yCONFIG_ADFS_FS=y
# CONFIG_ADFS_FS_RW is not setCONFIG_AFFS_FS=yCONFIG_HFS_FS=yCONFIG_HFSPLUS_FS=yCONFIG_BEFS_FS=y
# CONFIG_BEFS_DEBUG is not setCONFIG_BFS_FS=yCONFIG_EFS_FS=yCONFIG_CRAMFS=y
# CONFIG_SQUASHFS is not setCONFIG_VXFS_FS=yCONFIG_MINIX_FS=yCONFIG_OMFS_FS=y
# CONFIG_HPFS_FS is not setCONFIG_QNX4FS_FS=yCONFIG_ROMFS_FS=yCONFIG_SYSV_FS=y
# CONFIG_UFS_FS is not setCONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not setCONFIG_NFSD=yCONFIG_NFSD_V2_ACL=yCONFIG_NFSD_V3=yCONFIG_NFSD_V3_ACL=y
# CONFIG_NFSD_V4 is not setCONFIG_LOCKD=yCONFIG_LOCKD_V4=yCONFIG_EXPORTFS=yCONFIG_NFS_ACL_SUPPORT=yCONFIG_NFS_COMMON=yCONFIG_SUNRPC=yCONFIG_SUNRPC_GSS=yCONFIG_SUNRPC_REGISTER_V4=y
# CONFIG_RPCSEC_GSS_KRB5 is not setCONFIG_RPCSEC_GSS_SPKM3=y
# CONFIG_SMB_FS is not setCONFIG_CIFS=yCONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not setCONFIG_CIFS_WEAK_PW_HASH=yCONFIG_CIFS_XATTR=yCONFIG_CIFS_POSIX=yCONFIG_CIFS_DEBUG2=y
# CONFIG_CIFS_EXPERIMENTAL is not setCONFIG_NCP_FS=y
# CONFIG_NCPFS_PACKET_SIGNING is not setCONFIG_NCPFS_IOCTL_LOCKING=y
# CONFIG_NCPFS_STRONG is not setCONFIG_NCPFS_NFS_NS=yCONFIG_NCPFS_OS2_NS=yCONFIG_NCPFS_SMALLDOS=yCONFIG_NCPFS_NLS=yCONFIG_NCPFS_EXTRAS=y
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=yCONFIG_ACORN_PARTITION=yCONFIG_ACORN_PARTITION_CUMANA=y
# CONFIG_ACORN_PARTITION_EESOX is not setCONFIG_ACORN_PARTITION_ICS=yCONFIG_ACORN_PARTITION_ADFS=yCONFIG_ACORN_PARTITION_POWERTEC=yCONFIG_ACORN_PARTITION_RISCIX=y
# CONFIG_OSF_PARTITION is not setCONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not setCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=y
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not setCONFIG_UNIXWARE_DISKLABEL=yCONFIG_LDM_PARTITION=yCONFIG_LDM_DEBUG=yCONFIG_SGI_PARTITION=yCONFIG_ULTRIX_PARTITION=y
# CONFIG_SUN_PARTITION is not setCONFIG_KARMA_PARTITION=yCONFIG_EFI_PARTITION=yCONFIG_SYSV68_PARTITION=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not setCONFIG_NLS_CODEPAGE_775=y
# CONFIG_NLS_CODEPAGE_850 is not setCONFIG_NLS_CODEPAGE_852=yCONFIG_NLS_CODEPAGE_855=yCONFIG_NLS_CODEPAGE_857=yCONFIG_NLS_CODEPAGE_860=y
# CONFIG_NLS_CODEPAGE_861 is not setCONFIG_NLS_CODEPAGE_862=y
# CONFIG_NLS_CODEPAGE_863 is not setCONFIG_NLS_CODEPAGE_864=y
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not setCONFIG_NLS_CODEPAGE_869=y
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not setCONFIG_NLS_CODEPAGE_932=yCONFIG_NLS_CODEPAGE_949=y
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not setCONFIG_NLS_CODEPAGE_1250=y
# CONFIG_NLS_CODEPAGE_1251 is not setCONFIG_NLS_ASCII=yCONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not setCONFIG_NLS_ISO8859_5=y
# CONFIG_NLS_ISO8859_6 is not setCONFIG_NLS_ISO8859_7=y
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not setCONFIG_NLS_ISO8859_15=yCONFIG_NLS_KOI8_R=yCONFIG_NLS_KOI8_U=yCONFIG_NLS_UTF8=yCONFIG_DLM=yCONFIG_DLM_DEBUG=y
#
# Kernel hacking
#CONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_PRINTK_TIME=yCONFIG_ENABLE_WARN_DEPRECATED=y
# CONFIG_ENABLE_MUST_CHECK is not setCONFIG_FRAME_WARN=1024CONFIG_MAGIC_SYSRQ=yCONFIG_UNUSED_SYMBOLS=yCONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not setCONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not setCONFIG_DETECT_SOFTLOCKUP=yCONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=yCONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1CONFIG_SCHED_DEBUG=yCONFIG_SCHEDSTATS=yCONFIG_TIMER_STATS=yCONFIG_DEBUG_OBJECTS=yCONFIG_DEBUG_OBJECTS_SELFTEST=yCONFIG_DEBUG_OBJECTS_FREE=yCONFIG_DEBUG_OBJECTS_TIMERS=yCONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1CONFIG_SLUB_DEBUG_ON=yCONFIG_SLUB_STATS=yCONFIG_DEBUG_PREEMPT=yCONFIG_DEBUG_RT_MUTEXES=yCONFIG_DEBUG_PI_LIST=y
# CONFIG_RT_MUTEX_TESTER is not setCONFIG_DEBUG_SPINLOCK=yCONFIG_DEBUG_MUTEXES=yCONFIG_DEBUG_LOCK_ALLOC=yCONFIG_PROVE_LOCKING=yCONFIG_LOCKDEP=yCONFIG_LOCK_STAT=yCONFIG_DEBUG_LOCKDEP=yCONFIG_TRACE_IRQFLAGS=yCONFIG_DEBUG_SPINLOCK_SLEEP=yCONFIG_DEBUG_LOCKING_API_SELFTESTS=yCONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_INFO is not setCONFIG_DEBUG_VM=y
# CONFIG_DEBUG_VIRTUAL is not setCONFIG_DEBUG_WRITECOUNT=yCONFIG_DEBUG_MEMORY_INIT=yCONFIG_DEBUG_LIST=yCONFIG_DEBUG_SG=yCONFIG_DEBUG_NOTIFIERS=yCONFIG_ARCH_WANT_FRAME_POINTERS=yCONFIG_FRAME_POINTER=yCONFIG_BOOT_PRINTK_DELAY=y
# CONFIG_RCU_TORTURE_TEST is not setCONFIG_BACKTRACE_SELF_TEST=y
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not setCONFIG_FAULT_INJECTION=yCONFIG_FAILSLAB=y
# CONFIG_FAIL_PAGE_ALLOC is not set
# CONFIG_FAIL_MAKE_REQUEST is not setCONFIG_FAIL_IO_TIMEOUT=y
# CONFIG_FAULT_INJECTION_DEBUG_FS is not setCONFIG_LATENCYTOP=yCONFIG_SYSCTL_SYSCALL_CHECK=yCONFIG_USER_STACKTRACE_SUPPORT=yCONFIG_NOP_TRACER=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_HAVE_HW_BRANCH_TRACER=yCONFIG_TRACER_MAX_TRACE=yCONFIG_RING_BUFFER=yCONFIG_TRACING=y
#
# Tracers
#CONFIG_FUNCTION_TRACER=yCONFIG_FUNCTION_GRAPH_TRACER=yCONFIG_IRQSOFF_TRACER=y
# CONFIG_PREEMPT_TRACER is not setCONFIG_SYSPROF_TRACER=yCONFIG_SCHED_TRACER=yCONFIG_CONTEXT_SWITCH_TRACER=yCONFIG_BOOT_TRACER=y
# CONFIG_TRACE_BRANCH_PROFILING is not setCONFIG_POWER_TRACER=y
# CONFIG_STACK_TRACER is not setCONFIG_HW_BRANCH_TRACER=y
# CONFIG_DYNAMIC_FTRACE is not setCONFIG_MMIOTRACE=y
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not setCONFIG_DYNAMIC_PRINTK_DEBUG=yCONFIG_SAMPLES=y
# CONFIG_SAMPLE_KOBJECT is not setCONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not setCONFIG_STRICT_DEVMEM=yCONFIG_X86_VERBOSE_BOOTUP=yCONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not setCONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not setCONFIG_DEBUG_PAGEALLOC=yCONFIG_X86_PTDUMP=yCONFIG_DEBUG_RODATA=yCONFIG_DEBUG_RODATA_TEST=yCONFIG_4KSTACKS=y
# CONFIG_DOUBLEFAULT is not setCONFIG_HAVE_MMIOTRACE_SUPPORT=yCONFIG_IO_DELAY_TYPE_0X80=0CONFIG_IO_DELAY_TYPE_0XED=1CONFIG_IO_DELAY_TYPE_UDELAY=2CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not set
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not setCONFIG_IO_DELAY_NONE=yCONFIG_DEFAULT_IO_DELAY_TYPE=3
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not setCONFIG_OPTIMIZE_INLINING=y
#
# Security options
#
# CONFIG_KEYS is not setCONFIG_SECURITY=yCONFIG_SECURITYFS=yCONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not setCONFIG_SECURITY_PATH=yCONFIG_SECURITY_FILE_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not setCONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0
# CONFIG_SECURITY_SMACK is not setCONFIG_CRYPTO=y
#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not setCONFIG_CRYPTO_ALGAPI=yCONFIG_CRYPTO_ALGAPI2=yCONFIG_CRYPTO_AEAD=yCONFIG_CRYPTO_AEAD2=yCONFIG_CRYPTO_BLKCIPHER=yCONFIG_CRYPTO_BLKCIPHER2=yCONFIG_CRYPTO_HASH=yCONFIG_CRYPTO_HASH2=yCONFIG_CRYPTO_RNG=yCONFIG_CRYPTO_RNG2=yCONFIG_CRYPTO_MANAGER=yCONFIG_CRYPTO_MANAGER2=yCONFIG_CRYPTO_GF128MUL=yCONFIG_CRYPTO_NULL=yCONFIG_CRYPTO_CRYPTD=y
# CONFIG_CRYPTO_AUTHENC is not set
#
# Authenticated Encryption with Associated Data
#CONFIG_CRYPTO_CCM=y
# CONFIG_CRYPTO_GCM is not setCONFIG_CRYPTO_SEQIV=y
#
# Block modes
#CONFIG_CRYPTO_CBC=yCONFIG_CRYPTO_CTR=yCONFIG_CRYPTO_CTS=yCONFIG_CRYPTO_ECB=y
# CONFIG_CRYPTO_LRW is not setCONFIG_CRYPTO_PCBC=yCONFIG_CRYPTO_XTS=y
#
# Hash modes
#CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
#
# Digest
#CONFIG_CRYPTO_CRC32C=yCONFIG_CRYPTO_CRC32C_INTEL=yCONFIG_CRYPTO_MD4=yCONFIG_CRYPTO_MD5=yCONFIG_CRYPTO_MICHAEL_MIC=yCONFIG_CRYPTO_RMD128=yCONFIG_CRYPTO_RMD160=yCONFIG_CRYPTO_RMD256=y
# CONFIG_CRYPTO_RMD320 is not setCONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not setCONFIG_CRYPTO_SHA512=yCONFIG_CRYPTO_TGR192=yCONFIG_CRYPTO_WP512=y
#
# Ciphers
#CONFIG_CRYPTO_AES=yCONFIG_CRYPTO_AES_586=y
# CONFIG_CRYPTO_ANUBIS is not setCONFIG_CRYPTO_ARC4=yCONFIG_CRYPTO_BLOWFISH=y
# CONFIG_CRYPTO_CAMELLIA is not setCONFIG_CRYPTO_CAST5=yCONFIG_CRYPTO_CAST6=yCONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not setCONFIG_CRYPTO_KHAZAD=y
# CONFIG_CRYPTO_SALSA20 is not setCONFIG_CRYPTO_SALSA20_586=yCONFIG_CRYPTO_SEED=yCONFIG_CRYPTO_SERPENT=y
# CONFIG_CRYPTO_TEA is not setCONFIG_CRYPTO_TWOFISH=yCONFIG_CRYPTO_TWOFISH_COMMON=yCONFIG_CRYPTO_TWOFISH_586=y
#
# Compression
#CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_LZO is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not setCONFIG_CRYPTO_HW=yCONFIG_CRYPTO_DEV_PADLOCK=yCONFIG_CRYPTO_DEV_PADLOCK_AES=y
# CONFIG_CRYPTO_DEV_PADLOCK_SHA is not setCONFIG_CRYPTO_DEV_GEODE=y
# CONFIG_CRYPTO_DEV_HIFN_795X is not setCONFIG_HAVE_KVM=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=yCONFIG_KVM_INTEL=yCONFIG_KVM_AMD=yCONFIG_KVM_TRACE=yCONFIG_LGUEST=yCONFIG_VIRTIO=yCONFIG_VIRTIO_RING=yCONFIG_VIRTIO_PCI=y
# CONFIG_VIRTIO_BALLOON is not set
#
# Library routines
#CONFIG_BITREVERSE=yCONFIG_GENERIC_FIND_FIRST_BIT=yCONFIG_GENERIC_FIND_NEXT_BIT=yCONFIG_GENERIC_FIND_LAST_BIT=yCONFIG_CRC_CCITT=yCONFIG_CRC16=yCONFIG_CRC_T10DIF=yCONFIG_CRC_ITU_T=yCONFIG_CRC32=y
# CONFIG_CRC7 is not setCONFIG_LIBCRC32C=yCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=yCONFIG_PLIST=yCONFIG_HAS_IOMEM=yCONFIG_HAS_IOPORT=yCONFIG_HAS_DMA=y
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
(netdev Cc:-ed)
Quoted 6 lines · Ingo Molnar
Yesterday about half of my testboxes (3 out of 7) started getting weird networking failures: their network interface just got stuck completely - no rx and no tx at all. Restarting the interface did not help.
I've attached the reproducer (non-SMP) .config. The system has:
Note, the .config is randconfig derived. There was a stage of the tests when about every ~5-10th randconfig was failing, so i dont think it's a rare config combo that triggers this. (but there were other stages where 30 randconfig in a row went fine so it's hard to tell.)
In the worst case the hang needed 2 million packets to trigger - that's why i set the limit in the tests to 6 million packets.
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
In reply to Ingo MolnarQuoted 5 lines · Ingo Molnar
Yesterday about half of my testboxes (3 out of 7) started getting weird networking failures: their network interface just got stuck completely - no rx and no tx at all. Restarting the interface did not help.
Darn, does this patch help?
net: Fix netpoll lockup in legacy receive path
When I fixed the GRO crash in the legacy receive path I used napi_complete to replace __napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling __napi_complete at all.
While this is fishy in itself, let's make the obvious fix right now of reverting to the previous state where we always called __napi_complete.
net/core/dev.c +9 -7
@@ -2580,24 +2580,26 @@ static int process_backlog(struct napi_struct *napi, int quota)int work =0 ;struct softnet_data *queue = &__get_cpu_var (softnet_data);unsigned long start_time = jiffies; +struct sk_buff *skb; napi->weight = weight_p;do { -struct sk_buff *skb; -local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue); -if (!skb) { -local_irq_enable (); -napi_complete (napi); - goto out; - }local_irq_enable (); +if (!skb) +break ;napi_gro_receive (napi, skb); }while (++work < quota && jiffies == start_time);napi_gro_flush (napi); +if (skb) + goto out; + +local_irq_disable (); +__napi_complete (napi); +local_irq_enable (); out:return work;
Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtRe: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 10 lines · Herbert Xu
Quoted 5 lines · Ingo Molnar
Yesterday about half of my testboxes (3 out of 7) started getting weird networking failures: their network interface just got stuck completely - no rx and no tx at all. Restarting the interface did not help.
Darn, does this patch help?
net: Fix netpoll lockup in legacy receive path
thanks, added it to the test mix. Should know the result fin 1-2 hours test time.
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
In reply to Ingo MolnarQuoted 10 lines · Ingo Molnar
If the box hung within 15 minutes, the kernel was deemed bad. Using that method i arrived to this upstream networking fix which was merged yesterday:
| 303c6a0251852ecbdc5c15e466dcaff5971f7517 is first bad commit | commit 303c6a0251852ecbdc5c15e466dcaff5971f7517 | Author: Herbert Xu <[email protected]> | Date: Tue Mar 17 13:11:29 2009 -0700 | | gro: Fix legacy path napi_complete crash
This commit breaks nfsroot booting on i.MX27 and other ARM boxes with different network cards here in a reproducable way.
rsc
Signature · 4 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 12 lines · Robert Schwebel
Quoted 10 lines · Ingo Molnar
If the box hung within 15 minutes, the kernel was deemed bad. Using that method i arrived to this upstream networking fix which was merged yesterday:
| 303c6a0251852ecbdc5c15e466dcaff5971f7517 is first bad commit | commit 303c6a0251852ecbdc5c15e466dcaff5971f7517 | Author: Herbert Xu <[email protected]> | Date: Tue Mar 17 13:11:29 2009 -0700 | | gro: Fix legacy path napi_complete crash
Quoted 2 lines
This commit breaks nfsroot booting on i.MX27 and other ARM boxes with different network cards here in a reproducable way.
Can you confirm that Herbert's fix (see it below) solves the problem?
Ingo
--------------->
Quoted 1 line
From
b8b66ac07cab1b45aac93e4f406833a1e0d7677eMon Sep 17 00:00:00 2001
From: Herbert Xu <[email protected]>
Date: Tue, 24 Mar 2009 21:35:42 +0800
Subject: [PATCH] net: Fix netpoll lockup in legacy receive path
When I fixed the GRO crash in the legacy receive path I used napi_complete to replace __napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling __napi_complete at all.
While this is fishy in itself, let's make the obvious fix right now of reverting to the previous state where we always called __napi_complete.
LKML-Reference: <[email protected]>
--- net/core/dev.c | 16 +++++++++------- 1 files changed, 9 insertions(+), 7 deletions(-)
net/core/dev.c +9 -7
@@ -2580,24 +2580,26 @@ static int process_backlog(struct napi_struct *napi, int quota)int work =0 ;struct softnet_data *queue = &__get_cpu_var (softnet_data);unsigned long start_time = jiffies; +struct sk_buff *skb; napi->weight = weight_p;do { -struct sk_buff *skb; -local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue); -if (!skb) { -local_irq_enable (); -napi_complete (napi); - goto out; - }local_irq_enable (); +if (!skb) +break ;napi_gro_receive (napi, skb); }while (++work < quota && jiffies == start_time);napi_gro_flush (napi); +if (skb) + goto out; + +local_irq_disable (); +__napi_complete (napi); +local_irq_enable (); out:return work;
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 2 lines · Ingo Molnar
Subject: [PATCH] net: Fix netpoll lockup in legacy receive path
Actually, this patch is still racy. If some interrupt comes in and we suddenly get the maximum amount of backlog we can still hang when we call __napi_complete incorrectly. It's unlikely but we certainly shouldn't allow that. Here's a better version.
net: Fix netpoll lockup in legacy receive path
When I fixed the GRO crash in the legacy receive path I used napi_complete to replace __napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling __napi_complete at all.
What's more, we really do need to keep the __napi_complete call within the IRQ-off section since in theory an IRQ can occur in between and fill up the backlog to the maximum, causing us to lock up.
This patch fixes this by essentially open-coding __napi_complete.
Note we no longer need the memory barrier because this function is per-cpu.
net/core/dev.c +3 -3
@@ -2588,9 +2588,10 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +list_del (&napi->poll_list); +clear_bit (NAPI_STATE_SCHED , &napi->state);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();
@@ -2599,7 +2600,6 @@ static int process_backlog(struct napi_struct *napi, int quota)napi_gro_flush (napi); -out:return work; }
Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtSascha Hauer
Tested-byRe: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 8 lines · Herbert Xu
Quoted 2 lines · Ingo Molnar
Subject: [PATCH] net: Fix netpoll lockup in legacy receive path
Actually, this patch is still racy. If some interrupt comes in and we suddenly get the maximum amount of backlog we can still hang when we call
__napi_completeincorrectly. It's unlikely but we certainly shouldn't allow that. Here's a better version.
Yes, this one works. I always wanted to give a
Thanks
Sascha
Quoted 52 lines
net: Fix netpoll lockup in legacy receive path
When I fixed the GRO crash in the legacy receive path I used
napi_completeto replace__napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling__napi_completeat all.What's more, we really do need to keep the
__napi_completecall within the IRQ-off section since in theory an IRQ can occur in between and fill up the backlog to the maximum, causing us to lock up.This patch fixes this by essentially open-coding
__napi_complete.Note we no longer need the memory barrier because this function is per-cpu.
Signed-off-by Herbert Xu <[email protected]>net/core/dev.c +3
-3@@ -2588,9 +2588,10 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +list_del (&napi->poll_list); +clear_bit (NAPI_STATE_SCHED , &napi->state);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();@@ -2599,7 +2600,6 @@ static int process_backlog(struct napi_struct *napi, int quota)napi_gro_flush (napi); -out:return work; }Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[email protected]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Signature · 4 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
In reply to Herbert XuQuoted 10 lines · Herbert Xu
Quoted 2 lines · Ingo Molnar
Subject: [PATCH] net: Fix netpoll lockup in legacy receive path
Actually, this patch is still racy. If some interrupt comes in and we suddenly get the maximum amount of backlog we can still hang when we call
__napi_completeincorrectly. It's unlikely but we certainly shouldn't allow that. Here's a better version.net: Fix netpoll lockup in legacy receive path
ok - i'm testing with this now.
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 7 lines · Ingo Molnar
Quoted 4 lines · Herbert Xu
Quoted 2 lines · Ingo Molnar
Subject: [PATCH] net: Fix netpoll lockup in legacy receive path
Quoted 8 lines
Quoted 6 lines
Actually, this patch is still racy. If some interrupt comes in and we suddenly get the maximum amount of backlog we can still hang when we call
__napi_completeincorrectly. It's unlikely but we certainly shouldn't allow that. Here's a better version.net: Fix netpoll lockup in legacy receive path
ok - i'm testing with this now.
test failure on one of the boxes, interface got stuck after ~100K packets:
eth1 Link encap:Ethernet HWaddr 00:13:D4:DC:41:12
inet addr:10.0.1.13 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:d4ff:fedc:4112/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22555 errors:0 dropped:0 overruns:0 frame:0
TX packets:1897 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2435071 (2.3 MiB) TX bytes:503790 (491.9 KiB)
Interrupt:11 Base address:0x4000 i'm going back to your previous version for now - it might still be racy but it worked well for about 1.5 hours of test-time.
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 5 lines · Ingo Molnar
test failure on one of the boxes, interface got stuck after ~100K packets:
eth1 Link encap:Ethernet HWaddr 00:13:D4:DC:41:12
Quoted 8 lines
inet addr:10.0.1.13 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:d4ff:fedc:4112/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22555 errors:0 dropped:0 overruns:0 frame:0
TX packets:1897 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2435071 (2.3 MiB) TX bytes:503790 (491.9 KiB)
Interrupt:11 Base address:0x4000 What's the NIC and config on this one? If it's still using the legacy/netif_rx path, where GRO is off by default, this patch should make it exactly the same as with my original patch reverted.
Cheers,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtRe: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 15 lines · Herbert Xu
Quoted 5 lines · Ingo Molnar
test failure on one of the boxes, interface got stuck after ~100K packets:
eth1 Link encap:Ethernet HWaddr 00:13:D4:DC:41:12
Quoted 8 lines
inet addr:10.0.1.13 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::213:d4ff:fedc:4112/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22555 errors:0 dropped:0 overruns:0 frame:0 TX packets:1897 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2435071 (2.3 MiB) TX bytes:503790 (491.9 KiB) Interrupt:11 Base address:0x4000
Quoted 4 lines
What's the NIC and config on this one? If it's still using the legacy/netif_rx path, where GRO is off by default, this patch should make it exactly the same as with my original patch reverted.
Same forcedeth box i reported before. Config below. (note: if you want to use it you need to run it through 'make oldconfig', with all defaults accepted)
Ingo
# ac10134a # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29 # Tue Mar 24 15:24:33 2009 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_HAVE_DYNAMIC_PER_CPU_AREA=y # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_TRAMPOLINE=y CONFIG_X86_32_LAZY_GS=y CONFIG_KTIME_SCALAR=y # CONFIG_BOOTPARAM_SUPPORT_NOT_WANTED is not set CONFIG_BOOTPARAM_SUPPORT=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#CONFIG_EXPERIMENTAL=yCONFIG_BROKEN_BOOT_ALLOWED4=y
# CONFIG_BROKEN_BOOT_ALLOWED3 is not setCONFIG_BROKEN_BOOT_EUROPE=yCONFIG_BROKEN_BOOT_TITAN=yCONFIG_LOCK_KERNEL=yCONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not setCONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=y
# CONFIG_KERNEL_GZIP is not setCONFIG_KERNEL_BZIP2=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_SWAP is not setCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not setCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=y
# CONFIG_TASK_XACCT is not setCONFIG_AUDIT=y
# CONFIG_AUDITSYSCALL is not set
#
# RCU Subsystem
#CONFIG_CLASSIC_RCU=y
# CONFIG_TREE_RCU is not set
# CONFIG_PREEMPT_RCU is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_PREEMPT_RCU_TRACE is not setCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_LOG_BUF_SHIFT=20CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=yCONFIG_GROUP_SCHED=yCONFIG_FAIR_GROUP_SCHED=yCONFIG_RT_GROUP_SCHED=yCONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not setCONFIG_CGROUPS=yCONFIG_CGROUP_DEBUG=y
# CONFIG_CGROUP_NS is not setCONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CPUSETS is not setCONFIG_CGROUP_CPUACCT=y
# CONFIG_RESOURCE_COUNTERS is not setCONFIG_SYSFS_DEPRECATED=yCONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not setCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=y
# CONFIG_RD_BZIP2 is not set
# CONFIG_RD_LZMA is not setCONFIG_INITRAMFS_COMPRESSION_NONE=y
# CONFIG_INITRAMFS_COMPRESSION_GZIP is not set
# CONFIG_INITRAMFS_COMPRESSION_BZIP2 is not set
# CONFIG_INITRAMFS_COMPRESSION_LZMA is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_SYSCTL=yCONFIG_ANON_INODES=yCONFIG_EMBEDDED=y
# CONFIG_UID16 is not setCONFIG_SYSCTL_SYSCALL=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=yCONFIG_KALLSYMS_EXTRA_PASS=yCONFIG_HOTPLUG=yCONFIG_PRINTK=y
# CONFIG_BUG is not setCONFIG_ELF_CORE=y
# CONFIG_PCSPKR_PLATFORM is not setCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_EPOLL=yCONFIG_SIGNALFD=y
# CONFIG_TIMERFD is not set
# CONFIG_EVENTFD is not setCONFIG_SHMEM=y
# CONFIG_AIO is not setCONFIG_HAVE_PERF_COUNTERS=y
#
# Performance Counters
#CONFIG_PERF_COUNTERS=y
# CONFIG_EVENT_PROFILE is not setCONFIG_VM_EVENT_COUNTERS=yCONFIG_PCI_QUIRKS=y
# CONFIG_SLUB_DEBUG is not set
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_PROFILING=yCONFIG_TRACEPOINTS=yCONFIG_MARKERS=yCONFIG_OPROFILE=mCONFIG_OPROFILE_IBS=yCONFIG_HAVE_OPROFILE=yCONFIG_KPROBES=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_KRETPROBES=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_API_DEBUG=yCONFIG_HAVE_GENERIC_DMA_COHERENT=yCONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULES=yCONFIG_MODULE_FORCE_LOAD=yCONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not setCONFIG_MODULE_SRCVERSION_ALL=yCONFIG_STOP_MACHINE=yCONFIG_BLOCK=y
# CONFIG_LBD is not setCONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set
#
# IO Schedulers
#CONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_AS=yCONFIG_IOSCHED_DEADLINE=mCONFIG_IOSCHED_CFQ=m
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not setCONFIG_DEFAULT_NOOP=yCONFIG_DEFAULT_IOSCHED="noop"CONFIG_PREEMPT_NOTIFIERS=yCONFIG_FREEZER=y
#
# Processor type and features
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ=yCONFIG_BOOTPARAM_NO_HZ_OFF=y
# CONFIG_HIGH_RES_TIMERS is not setCONFIG_GENERIC_CLOCKEVENTS_BUILD=yCONFIG_BOOTPARAM_HIGHRES_OFF=yCONFIG_SMP_SUPPORT=yCONFIG_SPARSE_IRQ=yCONFIG_X86_MPPARSE=yCONFIG_X86_BIGSMP=y
# CONFIG_X86_EXTENDED_PLATFORM is not setCONFIG_SCHED_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not setCONFIG_MEMTEST=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not setCONFIG_MPENTIUMM=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not setCONFIG_X86_GENERIC=yCONFIG_X86_CPU=yCONFIG_X86_L1_CACHE_BYTES=64CONFIG_X86_INTERNODE_CACHE_BYTES=64CONFIG_X86_CMPXCHG=yCONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_XADD=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_X86_TSC=yCONFIG_X86_CMOV=yCONFIG_X86_MINIMUM_CPU_FAMILY=4CONFIG_X86_DEBUGCTLMSR=yCONFIG_PROCESSOR_SELECT=yCONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_CYRIX_32=yCONFIG_CPU_SUP_AMD=yCONFIG_CPU_SUP_CENTAUR=y
# CONFIG_CPU_SUP_TRANSMETA_32 is not set
# CONFIG_CPU_SUP_UMC_32 is not set
# CONFIG_X86_DS is not set
# CONFIG_X86_PTRACE_BTS is not set
# CONFIG_HPET_TIMER is not setCONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
# CONFIG_IOMMU_API is not setCONFIG_NR_CPUS=32CONFIG_SCHED_SMT=y
# CONFIG_SCHED_MC is not setCONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not setCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
# CONFIG_X86_MCE is not setCONFIG_VM86=yCONFIG_I8K=yCONFIG_X86_REBOOTFIXUPS=y
# CONFIG_MICROCODE is not setCONFIG_X86_MSR=mCONFIG_X86_CPUID=mCONFIG_X86_CPU_DEBUG=m
# CONFIG_UP_WANTED_1 is not setCONFIG_SMP=y
# CONFIG_NOHIGHMEM is not setCONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
# CONFIG_VMSPLIT_3G is not set
# CONFIG_VMSPLIT_3G_OPT is not setCONFIG_VMSPLIT_2G=y
# CONFIG_VMSPLIT_2G_OPT is not set
# CONFIG_VMSPLIT_1G is not setCONFIG_PAGE_OFFSET=0x80000000CONFIG_HIGHMEM=y
# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not setCONFIG_NEED_NODE_MEMMAP_SIZE=yCONFIG_ARCH_FLATMEM_ENABLE=yCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_ARCH_SELECT_MEMORY_MODEL=y
# CONFIG_ARCH_MEMORY_PROBE is not setCONFIG_ILLEGAL_POINTER_VALUE=0CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not setCONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=yCONFIG_HAVE_MEMORY_PRESENT=yCONFIG_SPARSEMEM_STATIC=yCONFIG_MEMORY_HOTPLUG=yCONFIG_MEMORY_HOTPLUG_SPARSE=yCONFIG_MEMORY_HOTREMOVE=yCONFIG_PAGEFLAGS_EXTENDED=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_MIGRATION=y
# CONFIG_PHYS_ADDR_T_64BIT is not setCONFIG_ZONE_DMA_FLAG=1CONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=y
# CONFIG_UNEVICTABLE_LRU is not setCONFIG_MMU_NOTIFIER=y
# CONFIG_HIGHPTE is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not setCONFIG_X86_RESERVE_LOW_64K=yCONFIG_MATH_EMULATION=yCONFIG_MTRR=yCONFIG_MTRR_SANITIZER=yCONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
# CONFIG_X86_PAT is not set
# CONFIG_SECCOMP is not set
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not setCONFIG_HZ_300=y
# CONFIG_HZ_1000 is not setCONFIG_HZ=300
# CONFIG_SCHED_HRTICK is not setCONFIG_KEXEC=yCONFIG_CRASH_DUMP=yCONFIG_PHYSICAL_START=0x100000CONFIG_RELOCATABLE=yCONFIG_PHYSICAL_ALIGN=0x100000CONFIG_HOTPLUG_CPU=yCONFIG_COMPAT_VDSO=yCONFIG_CMDLINE_BOOL=yCONFIG_CMDLINE=""CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
#
# Power management and ACPI options
#
# CONFIG_PM is not set
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=yCONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_USERSPACE=m CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
#
# CPUFreq processor drivers
#
# CONFIG_X86_POWERNOW_K6 is not setCONFIG_X86_POWERNOW_K7=mCONFIG_X86_POWERNOW_K8=yCONFIG_X86_GX_SUSPMOD=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not setCONFIG_X86_SPEEDSTEP_ICH=mCONFIG_X86_SPEEDSTEP_SMI=y
# CONFIG_X86_P4_CLOCKMOD is not setCONFIG_X86_CPUFREQ_NFORCE2=mCONFIG_X86_LONGRUN=yCONFIG_X86_E_POWERSAVER=y
#
# shared options # CONFIG_X86_SPEEDSTEP_LIB=y # CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK is not set # CONFIG_CPU_IDLE is not set
#
# Bus options (PCI etc.)
#CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not setCONFIG_PCI_GOMMCONFIG=y
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOOLPC is not set
# CONFIG_PCI_GOANY is not setCONFIG_PCI_BIOS=yCONFIG_PCI_DOMAINS=yCONFIG_PCIEPORTBUS=yCONFIG_PCIEAER=yCONFIG_PCIEASPM=yCONFIG_PCIEASPM_DEBUG=yCONFIG_ARCH_SUPPORTS_MSI=yCONFIG_PCI_MSI=y
# CONFIG_PCI_LEGACY is not set
# CONFIG_PCI_STUB is not set
# CONFIG_HT_IRQ is not setCONFIG_ISA_DMA_API=y
# CONFIG_ISA is not setCONFIG_MCA=yCONFIG_MCA_LEGACY=yCONFIG_MCA_PROC_FS=y
CONFIG_SCx200=y
CONFIG_SCx200HR_TIMER=y
# CONFIG_OLPC is not setCONFIG_K8_NB=yCONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not setCONFIG_PCMCIA=yCONFIG_PCMCIA_LOAD_CIS=yCONFIG_PCMCIA_IOCTL=y
# CONFIG_CARDBUS is not set
#
# PC-card bridges
#CONFIG_YENTA=y
# CONFIG_YENTA_O2 is not setCONFIG_YENTA_RICOH=yCONFIG_YENTA_TI=y
# CONFIG_YENTA_TOSHIBA is not set
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not setCONFIG_PCCARD_NONSTATIC=y
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_BOOTPARAM_NMI_WATCHDOG_BIT_0 is not setCONFIG_BOOTPARAM_NOLAPIC_TIMER=yCONFIG_BOOTPARAM_LAPIC=yCONFIG_BOOTPARAM_HPET_DISABLE=yCONFIG_BOOTPARAM_IDLE_MWAIT=yCONFIG_BOOTPARAM_IDLE_POLL=y
# CONFIG_BOOTPARAM_HIGHMEM_512M is not set
# CONFIG_BOOTPARAM_NOPAT is not setCONFIG_BOOTPARAM_NOTSC=y
# CONFIG_BOOTPARAM_ACPI_OFF is not set
# CONFIG_BOOTPARAM_PCI_NOMSI is not set
#
# Executable file formats / Emulations
#CONFIG_BINFMT_ELF=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_HAVE_AOUT=yCONFIG_BINFMT_AOUT=m
# CONFIG_BINFMT_MISC is not setCONFIG_HAVE_ATOMIC_IOMAP=yCONFIG_NET=y
#
# Networking options
#CONFIG_COMPAT_NET_DEV_OPS=yCONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not setCONFIG_UNIX=yCONFIG_XFRM=y
# CONFIG_XFRM_USER is not set CONFIG_XFRM_SUB_POLICY=y CONFIG_XFRM_MIGRATE=y CONFIG_XFRM_STATISTICS=yCONFIG_XFRM_IPCOMP=yCONFIG_NET_KEY=mCONFIG_NET_KEY_MIGRATE=yCONFIG_INET=y
# CONFIG_IP_MULTICAST is not set CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_MULTIPLE_TABLES=y
# CONFIG_IP_ROUTE_MULTIPATH is not set CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not setCONFIG_SYN_COOKIES=yCONFIG_INET_AH=yCONFIG_INET_ESP=y
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set CONFIG_INET_XFRM_MODE_TRANSPORT=y CONFIG_INET_XFRM_MODE_TUNNEL=m CONFIG_INET_XFRM_MODE_BEET=m CONFIG_INET_LRO=yCONFIG_INET_DIAG=yCONFIG_INET_TCP_DIAG=y CONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not set CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=yCONFIG_TCP_CONG_VENO=m
# CONFIG_TCP_CONG_YEAH is not set
# CONFIG_TCP_CONG_ILLINOIS is not set
# CONFIG_DEFAULT_BIC is not set CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" CONFIG_TCP_MD5SIG=yCONFIG_IPV6=yCONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_INET6_AH=yCONFIG_INET6_ESP=mCONFIG_INET6_IPCOMP=yCONFIG_IPV6_MIP6=yCONFIG_INET6_XFRM_TUNNEL=y CONFIG_INET6_TUNNEL=y
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set CONFIG_INET6_XFRM_MODE_TUNNEL=y
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set # CONFIG_IPV6_SIT is not set CONFIG_IPV6_TUNNEL=y
# CONFIG_IPV6_MULTIPLE_TABLES is not set CONFIG_IPV6_MROUTE=yCONFIG_IPV6_PIMSM_V2=yCONFIG_NETLABEL=y
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set CONFIG_IP_DCCP=yCONFIG_INET_DCCP_DIAG=y
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#CONFIG_IP_DCCP_CCID2_DEBUG=yCONFIG_IP_DCCP_CCID3=yCONFIG_IP_DCCP_CCID3_DEBUG=yCONFIG_IP_DCCP_CCID3_RTO=100CONFIG_IP_DCCP_TFRC_LIB=yCONFIG_IP_DCCP_TFRC_DEBUG=y
# CONFIG_IP_SCTP is not setCONFIG_TIPC=mCONFIG_TIPC_ADVANCED=yCONFIG_TIPC_ZONES=3CONFIG_TIPC_CLUSTERS=1CONFIG_TIPC_NODES=255CONFIG_TIPC_SLAVE_NODES=0CONFIG_TIPC_PORTS=8191CONFIG_TIPC_LOG=0
# CONFIG_TIPC_DEBUG is not setCONFIG_ATM=y
# CONFIG_ATM_CLIP is not set
# CONFIG_ATM_LANE is not set
# CONFIG_ATM_BR2684 is not setCONFIG_STP=yCONFIG_GARP=yCONFIG_BRIDGE=yCONFIG_NET_DSA=yCONFIG_NET_DSA_TAG_DSA=yCONFIG_NET_DSA_TAG_EDSA=y
# CONFIG_NET_DSA_TAG_TRAILER is not setCONFIG_NET_DSA_MV88E6XXX=y
# CONFIG_NET_DSA_MV88E6060 is not setCONFIG_NET_DSA_MV88E6XXX_NEED_PPU=yCONFIG_NET_DSA_MV88E6131=yCONFIG_NET_DSA_MV88E6123_61_65=yCONFIG_VLAN_8021Q=yCONFIG_VLAN_8021Q_GVRP=yCONFIG_DECNET=m
# CONFIG_DECNET_ROUTER is not setCONFIG_LLC=yCONFIG_LLC2=m
# CONFIG_IPX is not setCONFIG_ATALK=yCONFIG_DEV_APPLETALK=mCONFIG_IPDDP=mCONFIG_IPDDP_ENCAP=yCONFIG_IPDDP_DECAP=yCONFIG_X25=mCONFIG_LAPB=y
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not setCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#CONFIG_NET_SCH_CBQ=mCONFIG_NET_SCH_HTB=yCONFIG_NET_SCH_HFSC=mCONFIG_NET_SCH_ATM=m
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not setCONFIG_NET_SCH_RED=yCONFIG_NET_SCH_SFQ=y
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not setCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=y
# CONFIG_NET_SCH_NETEM is not setCONFIG_NET_SCH_DRR=yCONFIG_NET_SCH_INGRESS=y
#
# Classification
#CONFIG_NET_CLS=yCONFIG_NET_CLS_BASIC=yCONFIG_NET_CLS_TCINDEX=m
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not setCONFIG_NET_CLS_U32=yCONFIG_CLS_U32_PERF=yCONFIG_CLS_U32_MARK=yCONFIG_NET_CLS_RSVP=yCONFIG_NET_CLS_RSVP6=mCONFIG_NET_CLS_FLOW=mCONFIG_NET_CLS_CGROUP=y
# CONFIG_NET_EMATCH is not setCONFIG_NET_CLS_ACT=y
# CONFIG_NET_ACT_POLICE is not set
# CONFIG_NET_ACT_GACT is not setCONFIG_NET_ACT_MIRRED=mCONFIG_NET_ACT_NAT=yCONFIG_NET_ACT_PEDIT=m
# CONFIG_NET_ACT_SIMP is not setCONFIG_NET_ACT_SKBEDIT=mCONFIG_NET_CLS_IND=yCONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not setCONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
# CONFIG_AX25 is not setCONFIG_CAN=mCONFIG_CAN_RAW=m
# CONFIG_CAN_BCM is not set
#
# CAN Device Drivers
#
# CONFIG_CAN_VCAN is not setCONFIG_CAN_DEBUG_DEVICES=y
# CONFIG_IRDA is not setCONFIG_BT=y
# CONFIG_BT_L2CAP is not set
# CONFIG_BT_SCO is not set
#
# Bluetooth device drivers
#
# CONFIG_BT_HCIBTUSB is not setCONFIG_BT_HCIBTSDIO=mCONFIG_BT_HCIUART=yCONFIG_BT_HCIUART_H4=yCONFIG_BT_HCIUART_BCSP=yCONFIG_BT_HCIUART_LL=y
# CONFIG_BT_HCIBCM203X is not setCONFIG_BT_HCIBPA10X=mCONFIG_BT_HCIBFUSB=mCONFIG_BT_HCIDTL1=mCONFIG_BT_HCIBT3C=y
# CONFIG_BT_HCIBLUECARD is not setCONFIG_BT_HCIBTUART=m
# CONFIG_BT_HCIVHCI is not setCONFIG_AF_RXRPC=y
# CONFIG_AF_RXRPC_DEBUG is not setCONFIG_RXKAD=yCONFIG_PHONET=mCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_CFG80211=mCONFIG_CFG80211_REG_DEBUG=y
# CONFIG_NL80211 is not setCONFIG_WIRELESS_OLD_REGULATORY=yCONFIG_WIRELESS_EXT=yCONFIG_WIRELESS_EXT_SYSFS=yCONFIG_LIB80211=mCONFIG_LIB80211_DEBUG=yCONFIG_MAC80211=m
#
# Rate control algorithm selection
#
# CONFIG_MAC80211_RC_PID is not set CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT="minstrel"
# CONFIG_MAC80211_MESH is not set CONFIG_MAC80211_LEDS=y CONFIG_MAC80211_DEBUGFS=y CONFIG_MAC80211_DEBUG_MENU=y
# CONFIG_MAC80211_DEBUG_PACKET_ALIGNMENT is not set # CONFIG_MAC80211_NOINLINE is not set CONFIG_MAC80211_VERBOSE_DEBUG=y
# CONFIG_MAC80211_HT_DEBUG is not set CONFIG_MAC80211_TKIP_DEBUG=y
# CONFIG_MAC80211_IBSS_DEBUG is not set
# CONFIG_MAC80211_VERBOSE_PS_DEBUG is not set CONFIG_MAC80211_DEBUG_COUNTERS=y
# CONFIG_MAC80211_VERBOSE_SPECT_MGMT_DEBUG is not set CONFIG_WIMAX=mCONFIG_WIMAX_DEBUG_LEVEL=8
# CONFIG_RFKILL is not set
#
# Device Drivers
#
#
# Generic Driver Options
#CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"CONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=yCONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not setCONFIG_EXTRA_FIRMWARE=""
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not setCONFIG_PARPORT=y
# CONFIG_PARPORT_PC is not set
# CONFIG_PARPORT_GSC is not setCONFIG_PARPORT_AX88796=yCONFIG_PARPORT_1284=yCONFIG_PARPORT_NOT_PC=yCONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not setCONFIG_BLK_CPQ_DA=y
# CONFIG_BLK_CPQ_CISS_DA is not setCONFIG_BLK_DEV_DAC960=m
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not setCONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not setCONFIG_BLK_DEV_NBD=yCONFIG_BLK_DEV_SX8=yCONFIG_BLK_DEV_UB=mCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not setCONFIG_CDROM_PKTCDVD=yCONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not setCONFIG_ATA_OVER_ETH=yCONFIG_VIRTIO_BLK=mCONFIG_BLK_DEV_HD=yCONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not setCONFIG_PHANTOM=mCONFIG_SGI_IOC4=mCONFIG_TIFM_CORE=m
# CONFIG_TIFM_7XX1 is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not setCONFIG_C2PORT=mCONFIG_C2PORT_DURAMAR_2150=m
#
# EEPROM support
#CONFIG_EEPROM_AT24=mCONFIG_EEPROM_AT25=mCONFIG_EEPROM_LEGACY=yCONFIG_EEPROM_93CX6=yCONFIG_HAVE_IDE=y
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not setCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_TGT=mCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=yCONFIG_CHR_DEV_ST=mCONFIG_CHR_DEV_OSST=yCONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
# CONFIG_CHR_DEV_SG is not setCONFIG_CHR_DEV_SCH=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs #CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set CONFIG_SCSI_LOGGING=yCONFIG_SCSI_SCAN_ASYNC=yCONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=yCONFIG_SCSI_FC_ATTRS=yCONFIG_SCSI_ISCSI_ATTRS=y
# CONFIG_SCSI_SAS_ATTRS is not setCONFIG_SCSI_SRP_ATTRS=m
# CONFIG_SCSI_SRP_TGT_ATTRS is not setCONFIG_SCSI_LOWLEVEL=yCONFIG_ISCSI_TCP=mCONFIG_SCSI_CXGB3_ISCSI=mCONFIG_BLK_DEV_3W_XXXX_RAID=yCONFIG_SCSI_3W_9XXX=mCONFIG_SCSI_ACARD=yCONFIG_SCSI_AACRAID=yCONFIG_SCSI_AIC7XXX=yCONFIG_AIC7XXX_CMDS_PER_DEVICE=32CONFIG_AIC7XXX_RESET_DELAY_MS=5000CONFIG_AIC7XXX_DEBUG_ENABLE=yCONFIG_AIC7XXX_DEBUG_MASK=0CONFIG_AIC7XXX_REG_PRETTY_PRINT=yCONFIG_SCSI_AIC7XXX_OLD=yCONFIG_SCSI_AIC79XX=yCONFIG_AIC79XX_CMDS_PER_DEVICE=32CONFIG_AIC79XX_RESET_DELAY_MS=5000CONFIG_AIC79XX_DEBUG_ENABLE=yCONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_DPT_I2O is not setCONFIG_SCSI_ADVANSYS=yCONFIG_SCSI_ARCMSR=yCONFIG_SCSI_ARCMSR_AER=yCONFIG_MEGARAID_NEWGEN=y
# CONFIG_MEGARAID_MM is not setCONFIG_MEGARAID_LEGACY=y
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not setCONFIG_LIBFC=yCONFIG_FCOE=y
# CONFIG_SCSI_DMX3191D is not setCONFIG_SCSI_EATA=mCONFIG_SCSI_EATA_TAGGED_QUEUE=y
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not setCONFIG_SCSI_EATA_MAX_TAGS=16CONFIG_SCSI_FUTURE_DOMAIN=mCONFIG_SCSI_FD_MCS=yCONFIG_SCSI_GDTH=mCONFIG_SCSI_IBMMCA=yCONFIG_IBMMCA_SCSI_ORDER_STANDARD=yCONFIG_IBMMCA_SCSI_DEV_RESET=y
# CONFIG_SCSI_IPS is not setCONFIG_SCSI_INITIO=mCONFIG_SCSI_INIA100=m
# CONFIG_SCSI_NCR_D700 is not setCONFIG_SCSI_STEX=m
# CONFIG_SCSI_SYM53C8XX_2 is not setCONFIG_SCSI_IPR=mCONFIG_SCSI_IPR_TRACE=yCONFIG_SCSI_IPR_DUMP=yCONFIG_SCSI_NCR_Q720=yCONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32CONFIG_SCSI_NCR53C8XX_SYNC=20CONFIG_SCSI_QLOGIC_1280=mCONFIG_SCSI_QLA_FC=m
# CONFIG_SCSI_QLA_ISCSI is not setCONFIG_SCSI_LPFC=mCONFIG_SCSI_LPFC_DEBUG_FS=yCONFIG_SCSI_SIM710=y
CONFIG_SCSI_DC395x=mCONFIG_SCSI_DC390T=y
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not setCONFIG_SCSI_DH=yCONFIG_SCSI_DH_RDAC=m
# CONFIG_SCSI_DH_HP_SW is not setCONFIG_SCSI_DH_EMC=mCONFIG_SCSI_DH_ALUA=yCONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not setCONFIG_SATA_PMP=yCONFIG_SATA_AHCI=yCONFIG_SATA_SIL24=mCONFIG_ATA_SFF=yCONFIG_SATA_SVW=yCONFIG_ATA_PIIX=yCONFIG_SATA_MV=mCONFIG_SATA_NV=y
# CONFIG_PDC_ADMA is not setCONFIG_SATA_QSTOR=yCONFIG_SATA_PROMISE=yCONFIG_SATA_SX4=yCONFIG_SATA_SIL=y
# CONFIG_SATA_SIS is not setCONFIG_SATA_ULI=mCONFIG_SATA_VIA=mCONFIG_SATA_VITESSE=m
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not setCONFIG_PATA_AMD=y
# CONFIG_PATA_ARTOP is not setCONFIG_PATA_ATIIXP=mCONFIG_PATA_CMD640_PCI=mCONFIG_PATA_CMD64X=yCONFIG_PATA_CS5520=m
# CONFIG_PATA_CS5530 is not setCONFIG_PATA_CS5535=y
# CONFIG_PATA_CS5536 is not setCONFIG_PATA_CYPRESS=yCONFIG_PATA_EFAR=y
# CONFIG_ATA_GENERIC is not setCONFIG_PATA_HPT366=y
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not setCONFIG_PATA_HPT3X3=yCONFIG_PATA_HPT3X3_DMA=y
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not setCONFIG_PATA_JMICRON=y
# CONFIG_PATA_TRIFLEX is not setCONFIG_PATA_MARVELL=yCONFIG_PATA_MPIIX=mCONFIG_PATA_OLDPIIX=y
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not setCONFIG_PATA_NS87410=mCONFIG_PATA_NS87415=yCONFIG_PATA_OPTI=y
# CONFIG_PATA_OPTIDMA is not setCONFIG_PATA_PCMCIA=yCONFIG_PATA_PDC_OLD=m
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not setCONFIG_PATA_SC1200=yCONFIG_PATA_SERVERWORKS=m
# CONFIG_PATA_PDC2027X is not setCONFIG_PATA_SIL680=y
# CONFIG_PATA_SIS is not setCONFIG_PATA_VIA=mCONFIG_PATA_WINBOND=y
# CONFIG_PATA_PLATFORM is not setCONFIG_PATA_SCH=yCONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=mCONFIG_MD_RAID0=m
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not setCONFIG_MD_FAULTY=yCONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not setCONFIG_DM_CRYPT=m
# CONFIG_DM_SNAPSHOT is not setCONFIG_DM_MIRROR=mCONFIG_DM_ZERO=m
# CONFIG_DM_MULTIPATH is not setCONFIG_DM_DELAY=mCONFIG_DM_UEVENT=yCONFIG_FUSION=yCONFIG_FUSION_SPI=yCONFIG_FUSION_FC=y
# CONFIG_FUSION_SAS is not setCONFIG_FUSION_MAX_SGE=128CONFIG_FUSION_CTL=y
# CONFIG_FUSION_LOGGING is not set
#
# IEEE 1394 (FireWire) support
#
#
# Enable only one of the two stacks, unless you know what you are doing #CONFIG_FIREWIRE=mCONFIG_FIREWIRE_OHCI=mCONFIG_FIREWIRE_OHCI_DEBUG=yCONFIG_FIREWIRE_SBP2=m
# CONFIG_IEEE1394 is not setCONFIG_I2O=mCONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
# CONFIG_I2O_EXT_ADAPTEC is not set
# CONFIG_I2O_CONFIG is not setCONFIG_I2O_BUS=mCONFIG_I2O_BLOCK=m
# CONFIG_I2O_SCSI is not setCONFIG_I2O_PROC=mCONFIG_MACINTOSH_DRIVERS=y
# CONFIG_MAC_EMUMOUSEBTN is not setCONFIG_NETDEVICES=yCONFIG_IFB=mCONFIG_DUMMY=mCONFIG_BONDING=y
# CONFIG_MACVLAN is not setCONFIG_EQUALIZER=mCONFIG_TUN=yCONFIG_VETH=yCONFIG_ARCNET=y
# CONFIG_ARCNET_1201 is not set
# CONFIG_ARCNET_1051 is not setCONFIG_ARCNET_RAW=m
# CONFIG_ARCNET_CAP is not set
CONFIG_ARCNET_COM90xx=y
# CONFIG_ARCNET_COM90xxIO is not set
# CONFIG_ARCNET_RIM_I is not set
# CONFIG_ARCNET_COM20020 is not setCONFIG_PHYLIB=y
#
# MII PHY device drivers
#CONFIG_MARVELL_PHY=yCONFIG_DAVICOM_PHY=yCONFIG_QSEMI_PHY=yCONFIG_LXT_PHY=mCONFIG_CICADA_PHY=m
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set CONFIG_ICPLUS_PHY=yCONFIG_REALTEK_PHY=m
# CONFIG_NATIONAL_PHY is not set CONFIG_STE10XP=yCONFIG_LSI_ET1011C_PHY=m CONFIG_FIXED_PHY=y
# CONFIG_MDIO_BITBANG is not set CONFIG_NET_ETHERNET=yCONFIG_MII=yCONFIG_HAPPYMEAL=yCONFIG_SUNGEM=mCONFIG_CASSINI=m
# CONFIG_NET_VENDOR_3COM is not set CONFIG_VORTEX=yCONFIG_NET_VENDOR_SMC=y
# CONFIG_ULTRAMCA is not set CONFIG_ENC28J60=m CONFIG_ENC28J60_WRITEVERIFY=y
# CONFIG_DNET is not set CONFIG_NET_TULIP=yCONFIG_DE2104X=mCONFIG_TULIP=yCONFIG_TULIP_MWI=y
# CONFIG_TULIP_MMIO is not set CONFIG_TULIP_NAPI=y CONFIG_TULIP_NAPI_HW_MITIGATION=y CONFIG_DE4X5=yCONFIG_WINBOND_840=yCONFIG_DM9102=y
# CONFIG_ULI526X is not set CONFIG_AT1700=yCONFIG_DEPCA=yCONFIG_HP100=yCONFIG_NE2_MCA=yCONFIG_IBMLANA=y
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=yCONFIG_PCNET32=mCONFIG_AMD8111_ETH=y CONFIG_ADAPTEC_STARFIRE=m
# CONFIG_B44 is not setCONFIG_FORCEDETH=yCONFIG_FORCEDETH_NAPI=yCONFIG_E100=yCONFIG_FEALNX=mCONFIG_NATSEMI=mCONFIG_NE2K_PCI=mCONFIG_8139CP=mCONFIG_8139TOO=yCONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_R6040 is not setCONFIG_SIS900=m
# CONFIG_EPIC100 is not set
# CONFIG_SMSC9420 is not set CONFIG_SUNDANCE=mCONFIG_SUNDANCE_MMIO=y
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set CONFIG_NET_POCKET=yCONFIG_ATP=yCONFIG_DE600=y
# CONFIG_DE620 is not setCONFIG_ATL2=yCONFIG_NETDEV_1000=yCONFIG_ACENIC=y CONFIG_ACENIC_OMIT_TIGON_I=yCONFIG_DL2K=yCONFIG_E1000=mCONFIG_E1000E=yCONFIG_IP1000=yCONFIG_IGB=mCONFIG_IGB_LRO=y
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set CONFIG_R8169=mCONFIG_R8169_VLAN=yCONFIG_SIS190=yCONFIG_SKGE=mCONFIG_SKGE_DEBUG=yCONFIG_SKY2=yCONFIG_SKY2_DEBUG=yCONFIG_VIA_VELOCITY=mCONFIG_TIGON3=y
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not setCONFIG_ATL1=mCONFIG_ATL1E=m
# CONFIG_ATL1C is not setCONFIG_JME=yCONFIG_NETDEV_10000=yCONFIG_CHELSIO_T1=yCONFIG_CHELSIO_T1_1G=y CONFIG_CHELSIO_T3_DEPENDS=y CONFIG_CHELSIO_T3=y
# CONFIG_ENIC is not setCONFIG_IXGBE=yCONFIG_IXGB=yCONFIG_S2IO=yCONFIG_MYRI10GE=yCONFIG_NIU=y
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not setCONFIG_QLGE=mCONFIG_SFC=mCONFIG_BE2NET=mCONFIG_TR=y
# CONFIG_IBMTR is not setCONFIG_IBMOL=y
# CONFIG_IBMLS is not setCONFIG_3C359=y
# CONFIG_TMS380TR is not set
# CONFIG_SMCTR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_IWLWIFI_LEDS is not set
#
# WiMAX Wireless Broadband devices
#CONFIG_WIMAX_I2400M=mCONFIG_WIMAX_I2400M_SDIO=mCONFIG_WIMAX_I2400M_DEBUG_LEVEL=8
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not setCONFIG_USB_KAWETH=y
# CONFIG_USB_PEGASUS is not setCONFIG_USB_RTL8150=yCONFIG_USB_USBNET=yCONFIG_USB_NET_AX8817X=mCONFIG_USB_NET_CDCETHER=y
# CONFIG_USB_NET_DM9601 is not setCONFIG_USB_NET_SMSC95XX=yCONFIG_USB_NET_GL620A=m
# CONFIG_USB_NET_NET1080 is not setCONFIG_USB_NET_PLUSB=y
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not setCONFIG_USB_NET_CDC_SUBSET=mCONFIG_USB_ALI_M5632=y
# CONFIG_USB_AN2720 is not setCONFIG_USB_BELKIN=y
# CONFIG_USB_ARMLINUX is not set
# CONFIG_USB_EPSON2888 is not setCONFIG_USB_KC2190=yCONFIG_USB_NET_ZAURUS=yCONFIG_NET_PCMCIA=yCONFIG_PCMCIA_3C589=m
# CONFIG_PCMCIA_3C574 is not setCONFIG_PCMCIA_FMVJ18X=mCONFIG_PCMCIA_PCNET=yCONFIG_PCMCIA_NMCLAN=y
# CONFIG_PCMCIA_SMC91C92 is not setCONFIG_PCMCIA_XIRC2PS=m
# CONFIG_PCMCIA_AXNET is not setCONFIG_PCMCIA_IBMTR=y
# CONFIG_WAN is not set
# CONFIG_ATM_DRIVERS is not setCONFIG_FDDI=y
# CONFIG_DEFXX is not setCONFIG_SKFP=yCONFIG_HIPPI=yCONFIG_ROADRUNNER=yCONFIG_ROADRUNNER_LARGE_RINGS=yCONFIG_PLIP=mCONFIG_PPP=yCONFIG_PPP_MULTILINK=yCONFIG_PPP_FILTER=y
# CONFIG_PPP_ASYNC is not setCONFIG_PPP_SYNC_TTY=y
# CONFIG_PPP_DEFLATE is not setCONFIG_PPP_BSDCOMP=y
# CONFIG_PPP_MPPE is not setCONFIG_PPPOE=m
# CONFIG_PPPOATM is not setCONFIG_PPPOL2TP=m
# CONFIG_SLIP is not setCONFIG_SLHC=y
# CONFIG_NET_FC is not setCONFIG_NETCONSOLE=yCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not setCONFIG_NET_POLL_CONTROLLER=yCONFIG_VIRTIO_NET=yCONFIG_ISDN=y
# CONFIG_ISDN_I4L is not setCONFIG_ISDN_CAPI=yCONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
# CONFIG_CAPI_TRACE is not set
# CONFIG_ISDN_CAPI_MIDDLEWARE is not set
# CONFIG_ISDN_CAPI_CAPI20 is not set
#
# CAPI hardware drivers
#CONFIG_CAPI_AVM=yCONFIG_ISDN_DRV_AVMB1_B1PCI=yCONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
# CONFIG_ISDN_DRV_AVMB1_B1PCMCIA is not setCONFIG_ISDN_DRV_AVMB1_T1PCI=m
# CONFIG_ISDN_DRV_AVMB1_C4 is not setCONFIG_CAPI_EICON=yCONFIG_ISDN_DIVAS=yCONFIG_ISDN_DIVAS_BRIPCI=yCONFIG_ISDN_DIVAS_PRIPCI=y
# CONFIG_ISDN_DIVAS_DIVACAPI is not setCONFIG_ISDN_DIVAS_USERIDI=mCONFIG_ISDN_DIVAS_MAINT=mCONFIG_PHONE=m
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_FF_MEMLESS=mCONFIG_INPUT_POLLDEV=y
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ATKBD=yCONFIG_KEYBOARD_SUNKBD=mCONFIG_KEYBOARD_LKKBD=m
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not setCONFIG_KEYBOARD_STOWAWAY=yCONFIG_KEYBOARD_GPIO=mCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=y
# CONFIG_MOUSE_PS2_LIFEBOOK is not setCONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not setCONFIG_MOUSE_PS2_TOUCHKIT=yCONFIG_MOUSE_SERIAL=yCONFIG_MOUSE_APPLETOUCH=y
# CONFIG_MOUSE_BCM5974 is not setCONFIG_MOUSE_VSXXXAA=y
# CONFIG_MOUSE_GPIO is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not setCONFIG_INPUT_MISC=y
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_WISTRON_BTNS is not setCONFIG_INPUT_ATI_REMOTE=yCONFIG_INPUT_ATI_REMOTE2=yCONFIG_INPUT_KEYSPAN_REMOTE=yCONFIG_INPUT_POWERMATE=yCONFIG_INPUT_YEALINK=y
# CONFIG_INPUT_CM109 is not setCONFIG_INPUT_UINPUT=m
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=m
# CONFIG_SERIO_CT82C710 is not setCONFIG_SERIO_PARKBD=m
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=yCONFIG_SERIO_RAW=y
# CONFIG_GAMEPORT is not set
#
# Character devices
#CONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_DEVKMEM=yCONFIG_SERIAL_NONSTANDARD=yCONFIG_COMPUTONE=y
# CONFIG_ROCKETPORT is not setCONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not setCONFIG_MOXA_INTELLIO=m
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not setCONFIG_SYNCLINKMP=y
# CONFIG_SYNCLINK_GT is not setCONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not setCONFIG_SPECIALIX=yCONFIG_SX=m
# CONFIG_RIO is not setCONFIG_STALDRV=yCONFIG_STALLION=y
# CONFIG_ISTALLION is not setCONFIG_NOZOMI=m
#
# Serial drivers
#CONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_FIX_EARLYCON_MEM=y
# CONFIG_SERIAL_8250_PCI is not setCONFIG_SERIAL_8250_CS=yCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=4CONFIG_SERIAL_8250_EXTENDED=yCONFIG_SERIAL_8250_MANY_PORTS=yCONFIG_SERIAL_8250_SHARE_IRQ=yCONFIG_SERIAL_8250_DETECT_IRQ=yCONFIG_SERIAL_8250_RSA=yCONFIG_SERIAL_8250_MCA=y
#
# Non-8250 serial port support
#CONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not setCONFIG_UNIX98_PTYS=yCONFIG_DEVPTS_MULTIPLE_INSTANCES=y
# CONFIG_LEGACY_PTYS is not setCONFIG_PRINTER=yCONFIG_LP_CONSOLE=yCONFIG_PPDEV=yCONFIG_HVC_DRIVER=yCONFIG_VIRTIO_CONSOLE=y
# CONFIG_IPMI_HANDLER is not setCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_INTEL=mCONFIG_HW_RANDOM_AMD=mCONFIG_HW_RANDOM_GEODE=y
# CONFIG_HW_RANDOM_VIA is not setCONFIG_HW_RANDOM_VIRTIO=mCONFIG_NVRAM=y
# CONFIG_R3964 is not setCONFIG_APPLICOM=mCONFIG_SONYPI=m
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not setCONFIG_CARDMAN_4000=m
# CONFIG_CARDMAN_4040 is not setCONFIG_IPWIRELESS=mCONFIG_MWAVE=y
CONFIG_SCx200_GPIO=m
CONFIG_PC8736x_GPIO=mCONFIG_NSC_GPIO=mCONFIG_CS5535_GPIO=y
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not setCONFIG_TCG_TPM=m
# CONFIG_TCG_NSC is not setCONFIG_TCG_ATMEL=m
# CONFIG_TELCLOCK is not setCONFIG_DEVPORT=yCONFIG_I2C=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_CHARDEV=yCONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#CONFIG_I2C_ALI1535=mCONFIG_I2C_ALI1563=mCONFIG_I2C_ALI15X3=m
# CONFIG_I2C_AMD756 is not setCONFIG_I2C_AMD8111=yCONFIG_I2C_I801=y
# CONFIG_I2C_ISCH is not setCONFIG_I2C_PIIX4=m
# CONFIG_I2C_NFORCE2 is not setCONFIG_I2C_SIS5595=mCONFIG_I2C_SIS630=mCONFIG_I2C_SIS96X=y
# CONFIG_I2C_VIA is not setCONFIG_I2C_VIAPRO=m
#
# I2C system bus drivers (mostly embedded / system-on-chip) #CONFIG_I2C_GPIO=mCONFIG_I2C_OCORES=yCONFIG_I2C_SIMTEC=y
#
# External I2C/SMBus adapter drivers
#CONFIG_I2C_PARPORT=mCONFIG_I2C_PARPORT_LIGHT=m
# CONFIG_I2C_TAOS_EVM is not setCONFIG_I2C_TINY_USB=m
#
# Graphics adapter I2C/DDC channel drivers
#CONFIG_I2C_VOODOO3=y
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_PCA_PLATFORM=m
# CONFIG_I2C_STUB is not set
CONFIG_SCx200_I2C=m
CONFIG_SCx200_I2C_SCL=12
CONFIG_SCx200_I2C_SDA=13
# CONFIG_SCx200_ACB is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
# CONFIG_SENSORS_PCA9539 is not setCONFIG_SENSORS_PCF8591=yCONFIG_SENSORS_MAX6875=y
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not setCONFIG_I2C_DEBUG_ALGO=y
# CONFIG_I2C_DEBUG_BUS is not setCONFIG_I2C_DEBUG_CHIP=yCONFIG_SPI=yCONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#CONFIG_SPI_BITBANG=yCONFIG_SPI_BUTTERFLY=y
# CONFIG_SPI_GPIO is not setCONFIG_SPI_LM70_LLP=y
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not setCONFIG_SPI_TLE62X0=mCONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=yCONFIG_GPIOLIB=yCONFIG_GPIO_SYSFS=y
#
# Memory mapped GPIO expanders:
#
#
# I2C GPIO expanders:
#CONFIG_GPIO_MAX732X=y
# CONFIG_GPIO_PCA953X is not setCONFIG_GPIO_PCF857X=y
# CONFIG_GPIO_TWL4030 is not set
#
# PCI GPIO expanders:
#
# CONFIG_GPIO_BT8XX is not set
#
# SPI GPIO expanders:
#
# CONFIG_GPIO_MAX7301 is not setCONFIG_GPIO_MCP23S08=mCONFIG_W1=m
#
# 1-wire Bus Masters
#CONFIG_W1_MASTER_MATROX=mCONFIG_W1_MASTER_DS2490=mCONFIG_W1_MASTER_DS2482=mCONFIG_W1_MASTER_GPIO=m
#
# 1-wire Slaves
#CONFIG_W1_SLAVE_THERM=m
# CONFIG_W1_SLAVE_SMEM is not set
# CONFIG_W1_SLAVE_DS2431 is not set
# CONFIG_W1_SLAVE_DS2433 is not setCONFIG_W1_SLAVE_DS2760=m
# CONFIG_W1_SLAVE_BQ27000 is not setCONFIG_POWER_SUPPLY=yCONFIG_POWER_SUPPLY_DEBUG=y
# CONFIG_PDA_POWER is not setCONFIG_BATTERY_DS2760=m
CONFIG_BATTERY_BQ27x00=yCONFIG_BATTERY_DA9030=mCONFIG_HWMON=mCONFIG_HWMON_VID=mCONFIG_SENSORS_ABITUGURU=mCONFIG_SENSORS_ABITUGURU3=mCONFIG_SENSORS_AD7414=m
# CONFIG_SENSORS_AD7418 is not setCONFIG_SENSORS_ADCXX=mCONFIG_SENSORS_ADM1021=mCONFIG_SENSORS_ADM1025=mCONFIG_SENSORS_ADM1026=mCONFIG_SENSORS_ADM1029=mCONFIG_SENSORS_ADM1031=m
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7462 is not setCONFIG_SENSORS_ADT7470=mCONFIG_SENSORS_ADT7473=mCONFIG_SENSORS_ADT7475=mCONFIG_SENSORS_K8TEMP=m
# CONFIG_SENSORS_ASB100 is not setCONFIG_SENSORS_ATXP1=mCONFIG_SENSORS_DS1621=mCONFIG_SENSORS_I5K_AMB=mCONFIG_SENSORS_F71805F=mCONFIG_SENSORS_F71882FG=m
# CONFIG_SENSORS_F75375S is not setCONFIG_SENSORS_FSCHER=mCONFIG_SENSORS_FSCPOS=m
# CONFIG_SENSORS_FSCHMD is not setCONFIG_SENSORS_GL518SM=mCONFIG_SENSORS_GL520SM=m
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_IT87 is not setCONFIG_SENSORS_LM63=mCONFIG_SENSORS_LM70=mCONFIG_SENSORS_LM75=mCONFIG_SENSORS_LM77=mCONFIG_SENSORS_LM78=mCONFIG_SENSORS_LM80=mCONFIG_SENSORS_LM83=mCONFIG_SENSORS_LM85=mCONFIG_SENSORS_LM87=mCONFIG_SENSORS_LTC4245=mCONFIG_SENSORS_MAX1111=m
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not setCONFIG_SENSORS_PC87360=mCONFIG_SENSORS_PC87427=m
# CONFIG_SENSORS_SIS5595 is not setCONFIG_SENSORS_DME1737=m
# CONFIG_SENSORS_SMSC47M1 is not setCONFIG_SENSORS_SMSC47M192=mCONFIG_SENSORS_SMSC47B397=mCONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_THMC50 is not setCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_VT1211=mCONFIG_SENSORS_VT8231=mCONFIG_SENSORS_W83781D=mCONFIG_SENSORS_W83791D=mCONFIG_SENSORS_W83792D=mCONFIG_SENSORS_W83793=mCONFIG_SENSORS_W83L785TS=mCONFIG_SENSORS_W83L786NG=m
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not setCONFIG_SENSORS_HDAPS=mCONFIG_SENSORS_APPLESMC=m
# CONFIG_HWMON_DEBUG_CHIP is not setCONFIG_THERMAL=mCONFIG_THERMAL_HWMON=y
# CONFIG_WATCHDOG is not setCONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=y
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not setCONFIG_TPS65010=yCONFIG_TWL4030_CORE=y
# CONFIG_MFD_TMIO is not setCONFIG_PMIC_DA903X=yCONFIG_MFD_WM8400=y
# CONFIG_MFD_PCF50633 is not setCONFIG_REGULATOR=yCONFIG_REGULATOR_DEBUG=y
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not setCONFIG_REGULATOR_BQ24022=mCONFIG_REGULATOR_WM8400=y
# CONFIG_REGULATOR_DA903X is not set
#
# Multimedia devices
#
#
# Multimedia core support
#CONFIG_VIDEO_DEV=yCONFIG_VIDEO_V4L2_COMMON=yCONFIG_VIDEO_ALLOW_V4L1=yCONFIG_VIDEO_V4L1_COMPAT=yCONFIG_DVB_CORE=yCONFIG_VIDEO_MEDIA=y
#
# Multimedia drivers
#CONFIG_VIDEO_SAA7146=yCONFIG_VIDEO_SAA7146_VV=yCONFIG_MEDIA_ATTACH=yCONFIG_MEDIA_TUNER=y
# CONFIG_MEDIA_TUNER_CUSTOMIZE is not setCONFIG_MEDIA_TUNER_SIMPLE=yCONFIG_MEDIA_TUNER_TDA8290=yCONFIG_MEDIA_TUNER_TDA827X=mCONFIG_MEDIA_TUNER_TDA18271=mCONFIG_MEDIA_TUNER_TDA9887=yCONFIG_MEDIA_TUNER_TEA5761=yCONFIG_MEDIA_TUNER_TEA5767=yCONFIG_MEDIA_TUNER_MT20XX=yCONFIG_MEDIA_TUNER_MT2060=mCONFIG_MEDIA_TUNER_MT2266=mCONFIG_MEDIA_TUNER_QT1010=mCONFIG_MEDIA_TUNER_XC2028=yCONFIG_MEDIA_TUNER_XC5000=yCONFIG_MEDIA_TUNER_MXL5005S=mCONFIG_VIDEO_V4L2=yCONFIG_VIDEO_V4L1=yCONFIG_VIDEOBUF_GEN=yCONFIG_VIDEOBUF_DMA_SG=y
# CONFIG_VIDEO_CAPTURE_DRIVERS is not setCONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_GEMTEK_PCI is not setCONFIG_RADIO_MAXIRADIO=mCONFIG_RADIO_MAESTRO=yCONFIG_USB_DSBR=mCONFIG_USB_SI470X=mCONFIG_USB_MR800=y
# CONFIG_RADIO_TEA5764 is not setCONFIG_DVB_DYNAMIC_MINORS=yCONFIG_DVB_CAPTURE_DRIVERS=y
#
# Supported SAA7146 based PCI Adapters
#CONFIG_TTPCI_EEPROM=yCONFIG_DVB_AV7110=yCONFIG_DVB_AV7110_OSD=yCONFIG_DVB_BUDGET_CORE=y
# CONFIG_DVB_BUDGET is not set
# CONFIG_DVB_BUDGET_CI is not setCONFIG_DVB_BUDGET_AV=yCONFIG_DVB_BUDGET_PATCH=m
#
# Supported USB Adapters
#CONFIG_DVB_USB=mCONFIG_DVB_USB_DEBUG=yCONFIG_DVB_USB_A800=mCONFIG_DVB_USB_DIBUSB_MB=mCONFIG_DVB_USB_DIBUSB_MB_FAULTY=yCONFIG_DVB_USB_DIBUSB_MC=mCONFIG_DVB_USB_DIB0700=mCONFIG_DVB_USB_UMT_010=mCONFIG_DVB_USB_CXUSB=mCONFIG_DVB_USB_M920X=mCONFIG_DVB_USB_GL861=m
# CONFIG_DVB_USB_AU6610 is not setCONFIG_DVB_USB_DIGITV=m
# CONFIG_DVB_USB_VP7045 is not setCONFIG_DVB_USB_VP702X=mCONFIG_DVB_USB_GP8PSK=mCONFIG_DVB_USB_NOVA_T_USB2=m
# CONFIG_DVB_USB_TTUSB2 is not set
# CONFIG_DVB_USB_DTT200U is not setCONFIG_DVB_USB_OPERA1=m
# CONFIG_DVB_USB_DW2102 is not setCONFIG_DVB_USB_CINERGY_T2=mCONFIG_DVB_USB_ANYSEE=m
# CONFIG_DVB_USB_DTV5100 is not setCONFIG_DVB_USB_AF9015=mCONFIG_DVB_TTUSB_BUDGET=m
# CONFIG_DVB_TTUSB_DEC is not setCONFIG_DVB_SIANO_SMS1XXX=mCONFIG_DVB_SIANO_SMS1XXX_SMS_IDS=y
#
# Supported FlexCopII (B2C2) Adapters
#CONFIG_DVB_B2C2_FLEXCOP=mCONFIG_DVB_B2C2_FLEXCOP_PCI=mCONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set
#
# Supported BT878 Adapters
#
#
# Supported Pluto2 Adapters
#CONFIG_DVB_PLUTO2=y
#
# Supported SDMC DM1105 Adapters
#CONFIG_DVB_DM1105=y
#
# Supported DVB Frontends
#
#
# Customise DVB Frontends
#
# CONFIG_DVB_FE_CUSTOMISE is not set
#
# Multistandard (satellite) frontends
#CONFIG_DVB_STB0899=yCONFIG_DVB_STB6100=m
#
# DVB-S (satellite) frontends
#CONFIG_DVB_CX24110=mCONFIG_DVB_CX24123=mCONFIG_DVB_MT312=mCONFIG_DVB_S5H1420=mCONFIG_DVB_STV0288=yCONFIG_DVB_STB6000=yCONFIG_DVB_STV0299=yCONFIG_DVB_TDA8083=y
# CONFIG_DVB_TDA10086 is not setCONFIG_DVB_TDA8261=yCONFIG_DVB_VES1X93=yCONFIG_DVB_TUNER_ITD1000=mCONFIG_DVB_TUNER_CX24113=mCONFIG_DVB_TDA826X=yCONFIG_DVB_TUA6100=yCONFIG_DVB_CX24116=yCONFIG_DVB_SI21XX=y
#
# DVB-T (terrestrial) frontends
#CONFIG_DVB_SP8870=y
# CONFIG_DVB_SP887X is not setCONFIG_DVB_CX22700=mCONFIG_DVB_CX22702=mCONFIG_DVB_DRX397XD=mCONFIG_DVB_L64781=yCONFIG_DVB_TDA1004X=yCONFIG_DVB_NXT6000=yCONFIG_DVB_MT352=mCONFIG_DVB_ZL10353=mCONFIG_DVB_DIB3000MB=yCONFIG_DVB_DIB3000MC=yCONFIG_DVB_DIB7000M=mCONFIG_DVB_DIB7000P=yCONFIG_DVB_TDA10048=m
#
# DVB-C (cable) frontends
#CONFIG_DVB_VES1820=yCONFIG_DVB_TDA10021=yCONFIG_DVB_TDA10023=yCONFIG_DVB_STV0297=y
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #CONFIG_DVB_NXT200X=mCONFIG_DVB_OR51211=m
# CONFIG_DVB_OR51132 is not setCONFIG_DVB_BCM3510=mCONFIG_DVB_LGDT330X=mCONFIG_DVB_LGDT3304=yCONFIG_DVB_S5H1409=y
# CONFIG_DVB_AU8522 is not setCONFIG_DVB_S5H1411=y
#
# ISDB-T (terrestrial) frontends
#
# CONFIG_DVB_S921 is not set
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=yCONFIG_DVB_TUNER_DIB0070=m
#
# SEC control devices for DVB-S
#CONFIG_DVB_LNBP21=yCONFIG_DVB_ISL6405=mCONFIG_DVB_ISL6421=yCONFIG_DVB_LGS8GL5=m
#
# Tools to develop new frontends
#CONFIG_DVB_DUMMY_FE=mCONFIG_DVB_AF9013=yCONFIG_DAB=yCONFIG_USB_DABUSB=y
#
# Graphics support
#CONFIG_AGP=yCONFIG_AGP_ALI=m
# CONFIG_AGP_ATI is not setCONFIG_AGP_AMD=mCONFIG_AGP_AMD64=m
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not setCONFIG_AGP_VIA=m
# CONFIG_AGP_EFFICEON is not setCONFIG_DRM=yCONFIG_DRM_TDFX=y
# CONFIG_DRM_R128 is not setCONFIG_DRM_RADEON=y
# CONFIG_DRM_MGA is not setCONFIG_DRM_SIS=mCONFIG_DRM_VIA=yCONFIG_DRM_SAVAGE=mCONFIG_VGASTATE=mCONFIG_VIDEO_OUTPUT_CONTROL=yCONFIG_FB=m
# CONFIG_FIRMWARE_EDID is not setCONFIG_FB_DDC=m
# CONFIG_FB_BOOT_VESA_SUPPORT is not setCONFIG_FB_CFB_FILLRECT=mCONFIG_FB_CFB_COPYAREA=mCONFIG_FB_CFB_IMAGEBLIT=m
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not setCONFIG_FB_SYS_FILLRECT=mCONFIG_FB_SYS_COPYAREA=mCONFIG_FB_SYS_IMAGEBLIT=mCONFIG_FB_FOREIGN_ENDIAN=y
# CONFIG_FB_BOTH_ENDIAN is not setCONFIG_FB_BIG_ENDIAN=y
# CONFIG_FB_LITTLE_ENDIAN is not setCONFIG_FB_SYS_FOPS=mCONFIG_FB_DEFERRED_IO=yCONFIG_FB_HECUBA=mCONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not setCONFIG_FB_BACKLIGHT=yCONFIG_FB_MODE_HELPERS=yCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#CONFIG_FB_PM2=mCONFIG_FB_PM2_FIFO_DISCONNECT=yCONFIG_FB_CYBER2000=m
# CONFIG_FB_ARC is not setCONFIG_FB_N411=m
# CONFIG_FB_HGA is not setCONFIG_FB_S1D13XXX=mCONFIG_FB_NVIDIA=mCONFIG_FB_NVIDIA_I2C=yCONFIG_FB_NVIDIA_DEBUG=yCONFIG_FB_NVIDIA_BACKLIGHT=yCONFIG_FB_RIVA=mCONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not setCONFIG_FB_RIVA_BACKLIGHT=yCONFIG_FB_LE80578=mCONFIG_FB_CARILLO_RANCH=mCONFIG_FB_MATROX=mCONFIG_FB_MATROX_MILLENIUM=yCONFIG_FB_MATROX_MYSTIQUE=yCONFIG_FB_MATROX_G=yCONFIG_FB_MATROX_I2C=mCONFIG_FB_MATROX_MAVEN=mCONFIG_FB_MATROX_MULTIHEAD=yCONFIG_FB_ATY128=mCONFIG_FB_ATY128_BACKLIGHT=yCONFIG_FB_ATY=mCONFIG_FB_ATY_CT=y
# CONFIG_FB_ATY_GENERIC_LCD is not setCONFIG_FB_ATY_GX=y
# CONFIG_FB_ATY_BACKLIGHT is not set
# CONFIG_FB_S3 is not setCONFIG_FB_SAVAGE=mCONFIG_FB_SAVAGE_I2C=y
# CONFIG_FB_SAVAGE_ACCEL is not set
# CONFIG_FB_SIS is not setCONFIG_FB_VIA=m
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not setCONFIG_FB_VOODOO1=m
# CONFIG_FB_VT8623 is not setCONFIG_FB_TRIDENT=mCONFIG_FB_TRIDENT_ACCEL=yCONFIG_FB_ARK=mCONFIG_FB_PM3=m
# CONFIG_FB_CARMINE is not setCONFIG_FB_GEODE=yCONFIG_FB_GEODE_LX=mCONFIG_FB_GEODE_GX=m
# CONFIG_FB_GEODE_GX1 is not set
# CONFIG_FB_TMIO is not setCONFIG_FB_METRONOME=mCONFIG_FB_MB862XX=mCONFIG_FB_MB862XX_PCI_GDC=yCONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not setCONFIG_BACKLIGHT_CLASS_DEVICE=yCONFIG_BACKLIGHT_GENERIC=mCONFIG_BACKLIGHT_PROGEAR=yCONFIG_BACKLIGHT_DA903X=yCONFIG_BACKLIGHT_MBP_NVIDIA=y
# CONFIG_BACKLIGHT_SAHARA is not set
#
# Display device support
#CONFIG_DISPLAY_SUPPORT=y
#
# Display hardware drivers
#
#
# Console display driver support
#CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not setCONFIG_DUMMY_CONSOLE=yCONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not setCONFIG_LOGO_LINUX_VGA16=yCONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_SOUND is not setCONFIG_HID_SUPPORT=yCONFIG_HID=yCONFIG_HID_DEBUG=yCONFIG_HIDRAW=y
#
# USB Input Devices
#CONFIG_USB_HID=mCONFIG_HID_PID=yCONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#CONFIG_USB_KBD=yCONFIG_USB_MOUSE=y
#
# Special HID drivers
#CONFIG_HID_COMPAT=yCONFIG_HID_A4TECH=mCONFIG_HID_APPLE=m
# CONFIG_HID_BELKIN is not setCONFIG_HID_CHERRY=mCONFIG_HID_CHICONY=mCONFIG_HID_CYPRESS=m
# CONFIG_HID_EZKEY is not setCONFIG_HID_GYRATION=m
# CONFIG_HID_LOGITECH is not setCONFIG_HID_MICROSOFT=mCONFIG_HID_MONTEREY=m
# CONFIG_HID_NTRIG is not setCONFIG_HID_PANTHERLORD=mCONFIG_PANTHERLORD_FF=yCONFIG_HID_PETALYNX=mCONFIG_HID_SAMSUNG=mCONFIG_HID_SONY=mCONFIG_HID_SUNPLUS=mCONFIG_GREENASIA_FF=mCONFIG_HID_TOPSEED=mCONFIG_THRUSTMASTER_FF=m
# CONFIG_ZEROPLUS_FF is not setCONFIG_USB_SUPPORT=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=yCONFIG_USB_ARCH_HAS_EHCI=yCONFIG_USB=yCONFIG_USB_DEBUG=y
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not setCONFIG_USB_DYNAMIC_MINORS=y
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not setCONFIG_USB_OTG_BLACKLIST_HUB=yCONFIG_USB_MON=yCONFIG_USB_WUSB=yCONFIG_USB_WUSB_CBAF=mCONFIG_USB_WUSB_CBAF_DEBUG=y
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_EHCI_TT_NEWSCHED=yCONFIG_USB_OXU210HP_HCD=yCONFIG_USB_ISP116X_HCD=yCONFIG_USB_ISP1760_HCD=mCONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not setCONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_UHCI_HCD=yCONFIG_USB_U132_HCD=m
# CONFIG_USB_SL811_HCD is not setCONFIG_USB_R8A66597_HCD=yCONFIG_USB_HWA_HCD=y
#
# USB Device Class drivers
#CONFIG_USB_ACM=m
# CONFIG_USB_PRINTER is not setCONFIG_USB_WDM=mCONFIG_USB_TMC=m
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed; #
#
# see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=m CONFIG_USB_STORAGE_DEBUG=y # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set CONFIG_USB_STORAGE_ISD200=y # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set CONFIG_USB_STORAGE_SDDR55=y CONFIG_USB_STORAGE_JUMPSHOT=y # CONFIG_USB_STORAGE_ALAUDA is not set CONFIG_USB_STORAGE_ONETOUCH=y # CONFIG_USB_STORAGE_KARMA is not set CONFIG_USB_STORAGE_CYPRESS_ATACB=y CONFIG_USB_LIBUSUAL=y
#
# USB Imaging devices
#CONFIG_USB_MDC800=yCONFIG_USB_MICROTEK=y
#
# USB port drivers
#
# CONFIG_USB_USS720 is not setCONFIG_USB_SERIAL=mCONFIG_USB_EZUSB=yCONFIG_USB_SERIAL_GENERIC=yCONFIG_USB_SERIAL_AIRCABLE=mCONFIG_USB_SERIAL_ARK3116=mCONFIG_USB_SERIAL_BELKIN=mCONFIG_USB_SERIAL_CH341=m
# CONFIG_USB_SERIAL_WHITEHEAT is not setCONFIG_USB_SERIAL_DIGI_ACCELEPORT=mCONFIG_USB_SERIAL_CP2101=m
# CONFIG_USB_SERIAL_CYPRESS_M8 is not setCONFIG_USB_SERIAL_EMPEG=mCONFIG_USB_SERIAL_FTDI_SIO=mCONFIG_USB_SERIAL_FUNSOFT=mCONFIG_USB_SERIAL_VISOR=mCONFIG_USB_SERIAL_IPAQ=m
# CONFIG_USB_SERIAL_IR is not setCONFIG_USB_SERIAL_EDGEPORT=mCONFIG_USB_SERIAL_EDGEPORT_TI=mCONFIG_USB_SERIAL_GARMIN=m
# CONFIG_USB_SERIAL_IPW is not setCONFIG_USB_SERIAL_IUU=mCONFIG_USB_SERIAL_KEYSPAN_PDA=mCONFIG_USB_SERIAL_KEYSPAN=m
# CONFIG_USB_SERIAL_KLSI is not setCONFIG_USB_SERIAL_KOBIL_SCT=mCONFIG_USB_SERIAL_MCT_U232=mCONFIG_USB_SERIAL_MOS7720=m
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MOTOROLA is not setCONFIG_USB_SERIAL_NAVMAN=mCONFIG_USB_SERIAL_PL2303=mCONFIG_USB_SERIAL_OTI6858=m
# CONFIG_USB_SERIAL_SPCP8X5 is not setCONFIG_USB_SERIAL_HP4X=mCONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not setCONFIG_USB_SERIAL_SIEMENS_MPI=mCONFIG_USB_SERIAL_SIERRAWIRELESS=mCONFIG_USB_SERIAL_TI=m
# CONFIG_USB_SERIAL_CYBERJACK is not setCONFIG_USB_SERIAL_XIRCOM=mCONFIG_USB_SERIAL_OPTION=mCONFIG_USB_SERIAL_OMNINET=m
# CONFIG_USB_SERIAL_OPTICON is not setCONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#CONFIG_USB_EMI62=yCONFIG_USB_EMI26=m
# CONFIG_USB_ADUTUX is not setCONFIG_USB_SEVSEG=mCONFIG_USB_RIO500=mCONFIG_USB_LEGOTOWER=mCONFIG_USB_LCD=mCONFIG_USB_BERRY_CHARGE=mCONFIG_USB_LED=yCONFIG_USB_CYPRESS_CY7C63=mCONFIG_USB_CYTHERM=yCONFIG_USB_PHIDGET=m
# CONFIG_USB_PHIDGETKIT is not setCONFIG_USB_PHIDGETMOTORCONTROL=m
# CONFIG_USB_PHIDGETSERVO is not setCONFIG_USB_IDMOUSE=yCONFIG_USB_FTDI_ELAN=mCONFIG_USB_APPLEDISPLAY=y
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not setCONFIG_USB_TRANCEVIBRATOR=mCONFIG_USB_IOWARRIOR=m
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not setCONFIG_USB_VST=y
# CONFIG_USB_ATM is not set
#
# OTG and related infrastructure
#CONFIG_USB_OTG_UTILS=yCONFIG_USB_GPIO_VBUS=yCONFIG_TWL4030_USB=yCONFIG_UWB=yCONFIG_UWB_HWA=y
# CONFIG_UWB_WHCI is not setCONFIG_UWB_WLP=yCONFIG_UWB_I1480U=m
# CONFIG_UWB_I1480U_WLP is not setCONFIG_MMC=mCONFIG_MMC_DEBUG=yCONFIG_MMC_UNSAFE_RESUME=y
#
# MMC/SD/SDIO Card Drivers
#
# CONFIG_MMC_BLOCK is not set
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_SDHCI is not setCONFIG_MMC_WBSD=mCONFIG_MMC_TIFM_SD=mCONFIG_MMC_SDRICOH_CS=mCONFIG_MEMSTICK=mCONFIG_MEMSTICK_DEBUG=y
#
# MemoryStick drivers
#CONFIG_MEMSTICK_UNSAFE_RESUME=yCONFIG_MSPRO_BLOCK=m
#
# MemoryStick Host Controller Drivers
#CONFIG_MEMSTICK_TIFM_MS=mCONFIG_MEMSTICK_JMICRON_38X=mCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=m
#
# LED drivers
#CONFIG_LEDS_NET48XX=mCONFIG_LEDS_WRAP=mCONFIG_LEDS_ALIX2=mCONFIG_LEDS_PCA9532=m
# CONFIG_LEDS_GPIO is not setCONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_DA903X is not set
#
# LED Triggers
#CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not setCONFIG_LEDS_TRIGGER_HEARTBEAT=yCONFIG_LEDS_TRIGGER_BACKLIGHT=yCONFIG_LEDS_TRIGGER_DEFAULT_ON=mCONFIG_ACCESSIBILITY=yCONFIG_A11Y_BRAILLE_CONSOLE=y
# CONFIG_EDAC is not setCONFIG_RTC_LIB=mCONFIG_RTC_CLASS=m
#
# RTC interfaces
#
# CONFIG_RTC_INTF_SYSFS is not setCONFIG_RTC_INTF_PROC=yCONFIG_RTC_INTF_DEV=yCONFIG_RTC_INTF_DEV_UIE_EMUL=y
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#CONFIG_RTC_DRV_DS1307=m
# CONFIG_RTC_DRV_DS1374 is not setCONFIG_RTC_DRV_DS1672=m
# CONFIG_RTC_DRV_MAX6900 is not setCONFIG_RTC_DRV_RS5C372=mCONFIG_RTC_DRV_ISL1208=m
# CONFIG_RTC_DRV_X1205 is not setCONFIG_RTC_DRV_PCF8563=mCONFIG_RTC_DRV_PCF8583=m
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_TWL4030 is not setCONFIG_RTC_DRV_S35390A=m
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T94 is not setCONFIG_RTC_DRV_DS1305=mCONFIG_RTC_DRV_DS1390=mCONFIG_RTC_DRV_MAX6902=mCONFIG_RTC_DRV_R9701=mCONFIG_RTC_DRV_RS5C348=m
# CONFIG_RTC_DRV_DS3234 is not set
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not setCONFIG_RTC_DRV_DS1511=mCONFIG_RTC_DRV_DS1553=mCONFIG_RTC_DRV_DS1742=mCONFIG_RTC_DRV_STK17TA8=mCONFIG_RTC_DRV_M48T86=m
# CONFIG_RTC_DRV_M48T35 is not setCONFIG_RTC_DRV_M48T59=mCONFIG_RTC_DRV_BQ4802=mCONFIG_RTC_DRV_V3020=m
#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not setCONFIG_AUXDISPLAY=yCONFIG_UIO=y
# CONFIG_UIO_CIF is not set
# CONFIG_UIO_PDRV is not setCONFIG_UIO_PDRV_GENIRQ=y
# CONFIG_UIO_SMX is not setCONFIG_UIO_SERCOS3=mCONFIG_X86_PLATFORM_DEVICES=y
#
# Firmware Drivers
#CONFIG_EDD=m
# CONFIG_EDD_OFF is not set
# CONFIG_FIRMWARE_MEMMAP is not setCONFIG_DELL_RBU=yCONFIG_DCDBAS=yCONFIG_DMIID=yCONFIG_ISCSI_IBFT_FIND=yCONFIG_ISCSI_IBFT=y
#
# File systems
#CONFIG_EXT2_FS=yCONFIG_EXT2_FS_XATTR=yCONFIG_EXT2_FS_POSIX_ACL=yCONFIG_EXT2_FS_SECURITY=yCONFIG_EXT2_FS_XIP=yCONFIG_EXT3_FS=yCONFIG_EXT3_FS_XATTR=yCONFIG_EXT3_FS_POSIX_ACL=yCONFIG_EXT3_FS_SECURITY=yCONFIG_EXT4_FS=mCONFIG_EXT4DEV_COMPAT=y
# CONFIG_EXT4_FS_XATTR is not setCONFIG_FS_XIP=yCONFIG_JBD=yCONFIG_JBD_DEBUG=yCONFIG_JBD2=m
# CONFIG_JBD2_DEBUG is not setCONFIG_FS_MBCACHE=yCONFIG_REISERFS_FS=yCONFIG_REISERFS_CHECK=yCONFIG_REISERFS_PROC_INFO=y
# CONFIG_REISERFS_FS_XATTR is not setCONFIG_JFS_FS=yCONFIG_JFS_POSIX_ACL=y
# CONFIG_JFS_SECURITY is not setCONFIG_JFS_DEBUG=yCONFIG_JFS_STATISTICS=yCONFIG_FS_POSIX_ACL=yCONFIG_FILE_LOCKING=yCONFIG_XFS_FS=mCONFIG_XFS_QUOTA=yCONFIG_XFS_POSIX_ACL=yCONFIG_XFS_RT=yCONFIG_XFS_DEBUG=y
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_DNOTIFY is not set
# CONFIG_INOTIFY is not set
# CONFIG_QUOTA is not setCONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not setCONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not setCONFIG_GENERIC_ACL=y
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not setCONFIG_UDF_FS=mCONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#CONFIG_FAT_FS=y
# CONFIG_MSDOS_FS is not setCONFIG_VFAT_FS=yCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#CONFIG_PROC_FS=yCONFIG_PROC_KCORE=y
# CONFIG_PROC_VMCORE is not set
# CONFIG_PROC_SYSCTL is not set
# CONFIG_PROC_PAGE_MONITOR is not setCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_TMPFS_POSIX_ACL=yCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=yCONFIG_CONFIGFS_FS=yCONFIG_MISC_FILESYSTEMS=yCONFIG_ADFS_FS=yCONFIG_ADFS_FS_RW=yCONFIG_AFFS_FS=yCONFIG_ECRYPT_FS=mCONFIG_HFS_FS=mCONFIG_HFSPLUS_FS=mCONFIG_BEFS_FS=y
# CONFIG_BEFS_DEBUG is not setCONFIG_BFS_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not setCONFIG_SQUASHFS=yCONFIG_SQUASHFS_EMBEDDED=yCONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3CONFIG_VXFS_FS=y
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not setCONFIG_HPFS_FS=yCONFIG_QNX4FS_FS=mCONFIG_ROMFS_FS=m
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not setCONFIG_NETWORK_FILESYSTEMS=yCONFIG_NFS_FS=m
# CONFIG_NFS_V3 is not setCONFIG_NFS_V4=y
# CONFIG_NFSD is not setCONFIG_LOCKD=mCONFIG_EXPORTFS=mCONFIG_NFS_COMMON=yCONFIG_SUNRPC=mCONFIG_SUNRPC_GSS=mCONFIG_SUNRPC_REGISTER_V4=yCONFIG_RPCSEC_GSS_KRB5=mCONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not setCONFIG_CIFS=yCONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
# CONFIG_CIFS_WEAK_PW_HASH is not setCONFIG_CIFS_UPCALL=yCONFIG_CIFS_XATTR=y
# CONFIG_CIFS_POSIX is not setCONFIG_CIFS_DEBUG2=yCONFIG_CIFS_EXPERIMENTAL=yCONFIG_CIFS_DFS_UPCALL=yCONFIG_NCP_FS=m
# CONFIG_NCPFS_PACKET_SIGNING is not setCONFIG_NCPFS_IOCTL_LOCKING=yCONFIG_NCPFS_STRONG=yCONFIG_NCPFS_NFS_NS=yCONFIG_NCPFS_OS2_NS=y
# CONFIG_NCPFS_SMALLDOS is not setCONFIG_NCPFS_NLS=yCONFIG_NCPFS_EXTRAS=yCONFIG_CODA_FS=mCONFIG_AFS_FS=yCONFIG_AFS_DEBUG=y
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=yCONFIG_ACORN_PARTITION=yCONFIG_ACORN_PARTITION_CUMANA=y
# CONFIG_ACORN_PARTITION_EESOX is not setCONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not setCONFIG_ACORN_PARTITION_POWERTEC=y
# CONFIG_ACORN_PARTITION_RISCIX is not setCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not setCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not setCONFIG_ULTRIX_PARTITION=yCONFIG_SUN_PARTITION=y
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not setCONFIG_SYSV68_PARTITION=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not setCONFIG_NLS_CODEPAGE_775=y
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not setCONFIG_NLS_CODEPAGE_855=m
# CONFIG_NLS_CODEPAGE_857 is not setCONFIG_NLS_CODEPAGE_860=mCONFIG_NLS_CODEPAGE_861=mCONFIG_NLS_CODEPAGE_862=m
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not setCONFIG_NLS_CODEPAGE_936=m
# CONFIG_NLS_CODEPAGE_950 is not setCONFIG_NLS_CODEPAGE_932=mCONFIG_NLS_CODEPAGE_949=yCONFIG_NLS_CODEPAGE_874=yCONFIG_NLS_ISO8859_8=mCONFIG_NLS_CODEPAGE_1250=yCONFIG_NLS_CODEPAGE_1251=mCONFIG_NLS_ASCII=mCONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not setCONFIG_NLS_ISO8859_5=m
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not setCONFIG_NLS_ISO8859_13=mCONFIG_NLS_ISO8859_14=mCONFIG_NLS_ISO8859_15=mCONFIG_NLS_KOI8_R=yCONFIG_NLS_KOI8_U=yCONFIG_NLS_UTF8=m
# CONFIG_DLM is not set
#
# Kernel hacking
#CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ALLOW_WARNINGS is not setCONFIG_FRAME_WARN=1024CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not setCONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not setCONFIG_DEBUG_SECTION_MISMATCH=y
# CONFIG_DEBUG_KERNEL is not setCONFIG_SCHED_DEBUG=yCONFIG_SCHEDSTATS=yCONFIG_TRACE_IRQFLAGS=yCONFIG_STACKTRACE=yCONFIG_DEBUG_MEMORY_INIT=yCONFIG_ARCH_WANT_FRAME_POINTERS=yCONFIG_FRAME_POINTER=yCONFIG_RCU_CPU_STALL_DETECTOR=yCONFIG_LATENCYTOP=yCONFIG_SYSCTL_SYSCALL_CHECK=yCONFIG_USER_STACKTRACE_SUPPORT=yCONFIG_NOP_TRACER=yCONFIG_HAVE_FTRACE_NMI_ENTER=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_HAVE_FTRACE_SYSCALLS=yCONFIG_TRACER_MAX_TRACE=yCONFIG_RING_BUFFER=yCONFIG_FTRACE_NMI_ENTER=yCONFIG_TRACING=yCONFIG_TRACING_SUPPORT=y
#
# Tracers
#CONFIG_FUNCTION_TRACER=yCONFIG_FUNCTION_GRAPH_TRACER=yCONFIG_IRQSOFF_TRACER=yCONFIG_SYSPROF_TRACER=y
# CONFIG_SCHED_TRACER is not setCONFIG_CONTEXT_SWITCH_TRACER=yCONFIG_EVENT_TRACER=y
# CONFIG_FTRACE_SYSCALLS is not setCONFIG_BOOT_TRACER=yCONFIG_POWER_TRACER=y
# CONFIG_STACK_TRACER is not setCONFIG_KMEMTRACE=y
# CONFIG_WORKQUEUE_TRACER is not set
# CONFIG_BLK_DEV_IO_TRACE is not setCONFIG_DYNAMIC_FTRACE=yCONFIG_FTRACE_MCOUNT_RECORD=yCONFIG_FTRACE_SELFTEST=yCONFIG_FTRACE_STARTUP_TEST=yCONFIG_MMIOTRACE=yCONFIG_MMIOTRACE_TEST=mCONFIG_PROVIDE_OHCI1394_DMA_INIT=yCONFIG_FIREWIRE_OHCI_REMOTE_DMA=y
# CONFIG_DYNAMIC_PRINTK_DEBUG is not setCONFIG_DMA_API_DEBUG=yCONFIG_SAMPLES=yCONFIG_SAMPLE_MARKERS=mCONFIG_SAMPLE_TRACEPOINTS=m
# CONFIG_SAMPLE_KOBJECT is not set
# CONFIG_SAMPLE_KPROBES is not setCONFIG_HAVE_ARCH_KGDB=yCONFIG_HAVE_ARCH_KMEMCHECK=yCONFIG_STRICT_DEVMEM=yCONFIG_X86_VERBOSE_BOOTUP=yCONFIG_EARLY_PRINTK=yCONFIG_EARLY_PRINTK_DBGP=yCONFIG_4KSTACKS=yCONFIG_DOUBLEFAULT=yCONFIG_HAVE_MMIOTRACE_SUPPORT=yCONFIG_IO_DELAY_TYPE_0X80=0CONFIG_IO_DELAY_TYPE_0XED=1CONFIG_IO_DELAY_TYPE_UDELAY=2CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not setCONFIG_IO_DELAY_0XED=y
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not setCONFIG_DEFAULT_IO_DELAY_TYPE=1
# CONFIG_OPTIMIZE_INLINING is not set
#
# Security options
#CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not setCONFIG_SECURITY=yCONFIG_SECURITYFS=y
# CONFIG_SECURITY_NETWORK is not setCONFIG_SECURITY_PATH=yCONFIG_SECURITY_FILE_CAPABILITIES=yCONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0CONFIG_CRYPTO=y
#
# Crypto core or helper
#CONFIG_CRYPTO_FIPS=yCONFIG_CRYPTO_ALGAPI=yCONFIG_CRYPTO_ALGAPI2=yCONFIG_CRYPTO_AEAD=yCONFIG_CRYPTO_AEAD2=yCONFIG_CRYPTO_BLKCIPHER=yCONFIG_CRYPTO_BLKCIPHER2=yCONFIG_CRYPTO_HASH=yCONFIG_CRYPTO_HASH2=yCONFIG_CRYPTO_RNG=mCONFIG_CRYPTO_RNG2=yCONFIG_CRYPTO_MANAGER=yCONFIG_CRYPTO_MANAGER2=yCONFIG_CRYPTO_GF128MUL=yCONFIG_CRYPTO_NULL=m
# CONFIG_CRYPTO_CRYPTD is not setCONFIG_CRYPTO_AUTHENC=y
# CONFIG_CRYPTO_TEST is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not setCONFIG_CRYPTO_SEQIV=m
#
# Block modes
#CONFIG_CRYPTO_CBC=yCONFIG_CRYPTO_CTR=mCONFIG_CRYPTO_CTS=yCONFIG_CRYPTO_ECB=yCONFIG_CRYPTO_LRW=yCONFIG_CRYPTO_PCBC=yCONFIG_CRYPTO_XTS=m
#
# Hash modes
#CONFIG_CRYPTO_HMAC=yCONFIG_CRYPTO_XCBC=m
#
# Digest
#CONFIG_CRYPTO_CRC32C=yCONFIG_CRYPTO_CRC32C_INTEL=yCONFIG_CRYPTO_MD4=yCONFIG_CRYPTO_MD5=yCONFIG_CRYPTO_MICHAEL_MIC=mCONFIG_CRYPTO_RMD128=y
# CONFIG_CRYPTO_RMD160 is not setCONFIG_CRYPTO_RMD256=y
# CONFIG_CRYPTO_RMD320 is not setCONFIG_CRYPTO_SHA1=yCONFIG_CRYPTO_SHA256=mCONFIG_CRYPTO_SHA512=m
# CONFIG_CRYPTO_TGR192 is not setCONFIG_CRYPTO_WP512=y
#
# Ciphers
#CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_ANUBIS is not setCONFIG_CRYPTO_ARC4=mCONFIG_CRYPTO_BLOWFISH=mCONFIG_CRYPTO_CAMELLIA=yCONFIG_CRYPTO_CAST5=yCONFIG_CRYPTO_CAST6=yCONFIG_CRYPTO_DES=yCONFIG_CRYPTO_FCRYPT=yCONFIG_CRYPTO_KHAZAD=yCONFIG_CRYPTO_SALSA20=mCONFIG_CRYPTO_SALSA20_586=yCONFIG_CRYPTO_SEED=m
# CONFIG_CRYPTO_SERPENT is not setCONFIG_CRYPTO_TEA=y
# CONFIG_CRYPTO_TWOFISH is not setCONFIG_CRYPTO_TWOFISH_COMMON=yCONFIG_CRYPTO_TWOFISH_586=y
#
# Compression
#CONFIG_CRYPTO_DEFLATE=yCONFIG_CRYPTO_LZO=m
#
# Random Number Generation
#CONFIG_CRYPTO_ANSI_CPRNG=mCONFIG_CRYPTO_HW=yCONFIG_CRYPTO_DEV_PADLOCK=mCONFIG_CRYPTO_DEV_PADLOCK_AES=mCONFIG_CRYPTO_DEV_PADLOCK_SHA=m
# CONFIG_CRYPTO_DEV_GEODE is not setCONFIG_CRYPTO_DEV_HIFN_795X=yCONFIG_CRYPTO_DEV_HIFN_795X_RNG=yCONFIG_HAVE_KVM=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=yCONFIG_KVM_INTEL=mCONFIG_KVM_AMD=y
# CONFIG_KVM_TRACE is not setCONFIG_LGUEST=yCONFIG_VIRTIO=yCONFIG_VIRTIO_RING=yCONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_BALLOON=yCONFIG_BINARY_PRINTF=y
#
# Library routines
#CONFIG_BITREVERSE=yCONFIG_GENERIC_FIND_FIRST_BIT=yCONFIG_GENERIC_FIND_NEXT_BIT=yCONFIG_GENERIC_FIND_LAST_BIT=yCONFIG_CRC_CCITT=mCONFIG_CRC16=mCONFIG_CRC_T10DIF=yCONFIG_CRC_ITU_T=yCONFIG_CRC32=yCONFIG_CRC7=m
# CONFIG_LIBCRC32C is not setCONFIG_AUDIT_GENERIC=yCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=yCONFIG_LZO_COMPRESS=mCONFIG_LZO_DECOMPRESS=mCONFIG_DECOMPRESS_GZIP=yCONFIG_HAS_IOMEM=yCONFIG_HAS_IOPORT=yCONFIG_HAS_DMA=yCONFIG_CHECK_SIGNATURE=yCONFIG_FORCE_SUCCESSFUL_BUILD=yCONFIG_FORCE_MINIMAL_CONFIG=yCONFIG_FORCE_MINIMAL_CONFIG_PHYS=yCONFIG_X86_32_ALWAYS_ON=y
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 17 lines · Ingo Molnar
Quoted 15 lines · Herbert Xu
Quoted 13 lines · Ingo Molnar
test failure on one of the boxes, interface got stuck after ~100K packets:
eth1 Link encap:Ethernet HWaddr 00:13:D4:DC:41:12
inet addr:10.0.1.13 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::213:d4ff:fedc:4112/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22555 errors:0 dropped:0 overruns:0 frame:0 TX packets:1897 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2435071 (2.3 MiB) TX bytes:503790 (491.9 KiB) Interrupt:11 Base address:0x4000
Quoted 8 lines
Quoted 4 lines
What's the NIC and config on this one? If it's still using the legacy/netif_rx path, where GRO is off by default, this patch should make it exactly the same as with my original patch reverted.
Same forcedeth box i reported before. Config below. (note: if you want to use it you need to run it through 'make oldconfig', with all defaults accepted)
Hm, i justhad a test failure (hung interface) with this too.
I'll go back to the original straight revert of "303c6a0: gro: Fix legacy path napi_complete crash", and will test it overnight - to establish a baseline of stability again. (to make sure there are no other bugs interacting)
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
Quoted 10 lines · Ingo Molnar
Quoted 3 lines
Same forcedeth box i reported before. Config below. (note: if you want to use it you need to run it through 'make oldconfig', with all defaults accepted)
Hm, i just had a test failure (hung interface) with this too.
I'll go back to the original straight revert of "303c6a0: gro: Fix legacy path
napi_completecrash", and will test it overnight - to establish a baseline of stability again. (to make sure there are no other bugs interacting)
FYI, this plain revert is holding up fine in my tests so far - 50 random iterations - the previous one failed after 5 iterations.
Ingo
David Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: Ingo Molnar <[email protected]>
Date: Tue, 24 Mar 2009 21:54:44 +0100
Quoted 8 lines · Ingo Molnar
Quoted 7 lines
Quoted 4 lines
Same forcedeth box i reported before. Config below. (note: if you want to use it you need to run it through 'make oldconfig', with all defaults accepted)
Hm, i just had a test failure (hung interface) with this too.
Quoted 7 lines
Quoted 4 lines
I'll go back to the original straight revert of "303c6a0: gro: Fix legacy path
napi_completecrash", and will test it overnight - to establish a baseline of stability again. (to make sure there are no other bugs interacting)FYI, this plain revert is holding up fine in my tests so far - 50 random iterations - the previous one failed after 5 iterations.
Something must be up with respect to letting interrupts in during certain windows of time, or similar.
I'll take a look at this and hopefully Herbert or myself will be able to figure it out.
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 16 lines · David Miller
From: Ingo Molnar <[email protected]>
Date: Tue, 24 Mar 2009 21:54:44 +0100Quoted 13 lines · Ingo Molnar
Quoted 11 lines
Quoted 4 lines
Same forcedeth box i reported before. Config below. (note: if you want to use it you need to run it through 'make oldconfig', with all defaults accepted)
Hm, i just had a test failure (hung interface) with this too.
I'll go back to the original straight revert of "303c6a0: gro: Fix legacy path
napi_completecrash", and will test it overnight - to establish a baseline of stability again. (to make sure there are no other bugs interacting)
Quoted 8 lines
Quoted 2 lines
FYI, this plain revert is holding up fine in my tests so far - 50 random iterations - the previous one failed after 5 iterations.
Something must be up with respect to letting interrupts in during certain windows of time, or similar.
I'll take a look at this and hopefully Herbert or myself will be able to figure it out.
It definitely did not show usual patterns of bug behavior - i'd have found it yesterday morning if it did.
I spent most of the time trying to find a reliable reproducer .config and system. Sometimes the bug went away with a minor change in the .config. Until today i didnt even suspect a mainline change causing this.
Also, note that i have reduced the probability of UP kernels in my randconfigs artificially to about 12.5% (it is 50% upstream). Still, despite that measure, the 'best' .config i found was an UP config - i dont think that's an accident. Also, i had to fully saturate the target CPU over gigabit to hit the bug best.
Which suggests to me (empirically) that it's indeed a race and that it needs a saturated system with lots of IRQs to trigger, and perhaps that it needs saturated/overloaded network device queues and complex userspace/softirq/hardirq interactions.
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
In reply to Ingo MolnarQuoted 2 lines · Ingo Molnar
Hm, i justhad a test failure (hung interface) with this too.
Was this with NAPI on or off?
Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtRe: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
In reply to Ingo MolnarQuoted 8 lines · Ingo Molnar
Quoted 4 lines · Herbert Xu
What's the NIC and config on this one? If it's still using the legacy/netif_rx path, where GRO is off by default, this patch should make it exactly the same as with my original patch reverted.
Quoted 6 lines
Same forcedeth box i reported before. Config below. (note: if you want to use it you need to run it through 'make oldconfig', with all defaults accepted)
CONFIG_FORCEDETH=yCONFIG_FORCEDETH_NAPI=y
This means that we shouldn't even invoke netif_rx/process_backlog, so something else is going on.
Cheers,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtDavid Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: Herbert Xu <[email protected]>
Date: Wed, 25 Mar 2009 08:32:35 +0800
Quoted 13 lines · Ingo Molnar
Quoted 12 lines · Herbert Xu
Quoted 5 lines
What's the NIC and config on this one? If it's still using the legacy/netif_rx path, where GRO is off by default, this patch should make it exactly the same as with my original patch reverted.
Same forcedeth box i reported before. Config below. (note: if you want to use it you need to run it through 'make oldconfig', with all defaults accepted)
Quoted 5 lines
Quoted 2 lines
CONFIG_FORCEDETH=yCONFIG_FORCEDETH_NAPI=yThis means that we shouldn't even invoke netif_rx/process_backlog, so something else is going on.
There is always loopback which does netif_rx().
Combine that with the straight NAPI receive that forcedeth is doing here and I'm sure there are all kinds of race scenerios possible :-)
You're right about GRO not being relevant here. To be honest I wouldn't be disappointed if GRO was simply on by default even for the legacy paths.
David Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
In reply to Herbert XuFrom: Herbert Xu <[email protected]>
Date: Tue, 24 Mar 2009 23:09:28 +0800
Quoted 10 lines · Ingo Molnar
Quoted 2 lines
Subject: [PATCH] net: Fix netpoll lockup in legacy receive path
Actually, this patch is still racy. If some interrupt comes in and we suddenly get the maximum amount of backlog we can still hang when we call
__napi_completeincorrectly. It's unlikely but we certainly shouldn't allow that. Here's a better version.net: Fix netpoll lockup in legacy receive path
Hmmm...
net/core/dev.c static int process_backlog(struct napi_struct *napi, int quota) · line 2596
Quoted 12 lines
net/core/dev.c +3
-2@@ -2588,9 +2588,10 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +list_del (&napi->poll_list); +clear_bit (NAPI_STATE_SCHED , &napi->state);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();
I think the problem is that we need to do the GRO flush before the list delete and clearing the NAPI_STATE_SCHED bit.
You can't disown the NAPI context until you've squared away the GRO state, I think.
Ingo's case stresses TCP a lot so I think he's hitting these GRO cases a lot as well as hitting the backlog maximum.
So this mis-ordering of completion operations could explain why he still sees problems.
David Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: David Miller <[email protected]>
Date: Tue, 24 Mar 2009 14:36:22 -0700 (PDT)
Quoted 18 lines
From: Herbert Xu <[email protected]>
Date: Tue, 24 Mar 2009 23:09:28 +0800net/core/dev.c static int process_backlog(struct napi_struct *napi, int quota) · line 2596
Quoted 12 lines
net/core/dev.c +3
-2@@ -2588,9 +2588,10 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +list_del (&napi->poll_list); +clear_bit (NAPI_STATE_SCHED , &napi->state);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();I think the problem is that we need to do the GRO flush before the list delete and clearing the
NAPI_STATE_SCHEDbit.
Ok Herbert, I'm even more sure of this because in your original commit log message you mention:
This simply doesn't work since we need to flush the held GRO packets first.
We are certainly in a pickle here, actually.
We can't run the GRO flush until we re-enable interrupts. But if we re-enable interrupts, more packets get queued to the input_pkt_queue and we end up back where we started.
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 9 lines · David Miller
Quoted 3 lines
I think the problem is that we need to do the GRO flush before the list delete and clearing the
NAPI_STATE_SCHEDbit.Ok Herbert, I'm even more sure of this because in your original commit log message you mention:
This simply doesn't work since we need to flush the held GRO packets first.
That's only because I was calling __napi_complete, which is used by drivers in general so I added the check to ensure that GRO packets have been flushed. Now that we're open-coding it this is no longer a requirement.
But what's more GRO should be off on Ingo's test machines because we haven't added anything to turn it on by default for non-NAPI drivers.
Cheers,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtRe: Revert "gro: Fix legacy path napi_complete crash",
In reply to David MillerQuoted 3 lines · David Miller
I think the problem is that we need to do the GRO flush before the list delete and clearing the
NAPI_STATE_SCHEDbit.
Well first of all GRO shouldn't even be on in Ingo's case, unless he enabled it by hand with ethtool. Secondly the only thing that touches the GRO state for the legacy path is process_backlog, and since this is per-cpu, I can't see how another instance can run while the first is still going.
Cheers,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtDavid Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: Herbert Xu <[email protected]>
Date: Wed, 25 Mar 2009 08:23:03 +0800
Quoted 10 lines · David Miller
Quoted 3 lines
I think the problem is that we need to do the GRO flush before the list delete and clearing the
NAPI_STATE_SCHEDbit.Well first of all GRO shouldn't even be on in Ingo's case, unless he enabled it by hand with ethtool. Secondly the only thing that touches the GRO state for the legacy path is
process_backlog, and since this is per-cpu, I can't see how another instance can run while the first is still going.
Right.
I think the conditions Ingo is running under is that both loopback (using legacy paths) and his NAPI based device (forcedeth) are processing a lot of packets at the same time.
Another thing that seems to be critical is he can only trigger this on UP, which means that we don't have the damn APIC potentially moving the cpu target of the forcedeth interrupts around. And this means also that all the processing will be on one cpu's backlog queue only.
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 20 lines · David Miller
From: Herbert Xu <[email protected]>
Date: Wed, 25 Mar 2009 08:23:03 +0800Quoted 10 lines · David Miller
Quoted 3 lines
I think the problem is that we need to do the GRO flush before the list delete and clearing the
NAPI_STATE_SCHEDbit.Well first of all GRO shouldn't even be on in Ingo's case, unless he enabled it by hand with ethtool. Secondly the only thing that touches the GRO state for the legacy path is
process_backlog, and since this is per-cpu, I can't see how another instance can run while the first is still going.Right.
I think the conditions Ingo is running under is that both loopback (using legacy paths) and his NAPI based device (forcedeth) are processing a lot of packets at the same time.
Quoted 5 lines
Another thing that seems to be critical is he can only trigger this on UP, which means that we don't have the damn APIC potentially moving the cpu target of the forcedeth interrupts around. And this means also that all the processing will be on one cpu's backlog queue only.
I tested the plain revert i sent in the original report overnight (with about 12 hours of combined testing time), and all systems held up fine. The system that would reproduce the bug within 10-20 iterations did 210 successful iterations. Other systems held up fine too.
So if there's no definitive resolution for the real cause of the bug, the plain revert looks like an acceptable interim choice for .29.1 - at least as far as my systems go.
Ingo
David Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: Ingo Molnar <[email protected]>
Date: Wed, 25 Mar 2009 08:33:49 +0100
Quoted 3 lines
So if there's no definitive resolution for the real cause of the bug, the plain revert looks like an acceptable interim choice for .29.1 - at least as far as my systems go.
Then we get back the instant OOPS that patch fixes :-)
I'm sure Herbert will look into fixing this properly.
Re: Revert "gro: Fix legacy path napi_complete crash",
In reply to Ingo MolnarQuoted 4 lines · Ingo Molnar
So if there's no definitive resolution for the real cause of the bug, the plain revert looks like an acceptable interim choice for .29.1 - at least as far as my systems go.
OK, let's just do the revert and disable GRO for the legacy path. This should be the safest option for 2.6.29.
GRO: Disable GRO on legacy netif_rx path
When I fixed the GRO crash in the legacy receive path I used napi_complete to replace __napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling __napi_complete at all.
What's more, we really do need to keep the __napi_complete call within the IRQ-off section since in theory an IRQ can occur in between and fill up the backlog to the maximum, causing us to lock up.
Since we can't seem to find a fix that works properly right now, this patch reverts all the GRO support from the netif_rx path.
net/core/dev.c +3 -6
@@ -2588,18 +2588,15 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +__napi_complete (napi);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable (); -napi_gro_receive (napi, skb); +netif_receive_skb (skb); }while (++work < quota && jiffies == start_time); -napi_gro_flush (napi); - -out:return work; }
Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtRe: Revert "gro: Fix legacy path napi_complete crash",
Quoted 8 lines · Herbert Xu
Quoted 4 lines · Ingo Molnar
So if there's no definitive resolution for the real cause of the bug, the plain revert looks like an acceptable interim choice for .29.1 - at least as far as my systems go.
OK, let's just do the revert and disable GRO for the legacy path. This should be the safest option for 2.6.29.
ok - i have started testing the delta below, on top of the plain revert.
Ingo
net/core/dev.c +1 -3
@@ -2594,11 +2594,9 @@ static int process_backlog(struct napi_struct *napi, int quota) }local_irq_enable (); -napi_gro_receive (napi, skb); +netif_receive_skb (skb); }while (++work < quota && jiffies == start_time); -napi_gro_flush (napi); -return work; }
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 3 lines · Ingo Molnar
ok - i have started testing the delta below, on top of the plain revert.
Thanks! BTW Ingo, any chance you could help us identify the problem with the previous patch? I don't have a forcedeth machine here and the hang you had with my patch that open-coded __napi_complete appears intimately connected to forcedeth (with NAPI enabled).
The simplest thing to try would be to build forcedeth.c with DEBUG and see what it prints out after it locks up.
Cheers,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtIngo Molnar
Tested-byRe: Revert "gro: Fix legacy path napi_complete crash",
Quoted 4 lines · Herbert Xu
Quoted 3 lines · Ingo Molnar
ok - i have started testing the delta below, on top of the plain revert.
it's still fine btw, so:
Quoted 8 lines
Thanks! BTW Ingo, any chance you could help us identify the problem with the previous patch? I don't have a forcedeth machine here and the hang you had with my patch that open-coded
__napi_completeappears intimately connected to forcedeth (with NAPI enabled).The simplest thing to try would be to build
forcedeth.cwith DEBUG and see what it prints out after it locks up.
Sure, can try that. Probably the best would be if you sent me a combo patch with the precise patch you meant me to try (there were several patches, i'm not sure which one is the 'previous' one) plus the forcedeth debug enable change as well.
Thanks,
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 11 lines · Ingo Molnar
Quoted 4 lines · Herbert Xu
Quoted 3 lines · Ingo Molnar
ok - i have started testing the delta below, on top of the plain revert.
it's still fine btw, so:
Tested-by Ingo Molnar <[email protected]>
I saw your patch this morning and added it to my system too. 4 hours and 15 minutes and everything is still fine here.
CONFIG_FORCEDETH=y
# CONFIG_FORCEDETH_NAPI is not set
with
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
Re: Revert "gro: Fix legacy path napi_complete crash",
In reply to Ingo MolnarQuoted 5 lines · Ingo Molnar
Sure, can try that. Probably the best would be if you sent me a combo patch with the precise patch you meant me to try (there were several patches, i'm not sure which one is the 'previous' one) plus the forcedeth debug enable change as well.
Sure, here's the patch to do both.
net/core/dev.c +3 -3
@@ -2588,9 +2588,10 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +list_del (&napi->poll_list); +clear_bit (NAPI_STATE_SCHED , &napi->state);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();
@@ -2599,7 +2600,6 @@ static int process_backlog(struct napi_struct *napi, int quota)napi_gro_flush (napi); -out:return work; }
drivers/net/forcedeth.c +1 -1
@@ -64,7 +64,7 @@#include <asm/uaccess.h> #include <asm/system.h> -#if 0 +#if 1 #define dprintk printk#else #define dprintk(x...) do { } while (0)
Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtRe: Revert "gro: Fix legacy path napi_complete crash",
Quoted 14 lines · Herbert Xu
Quoted 5 lines · Ingo Molnar
Sure, can try that. Probably the best would be if you sent me a combo patch with the precise patch you meant me to try (there were several patches, i'm not sure which one is the 'previous' one) plus the forcedeth debug enable change as well.
Sure, here's the patch to do both.
drivers/net/forcedeth.c +0
-0
drivers/net/forcedeth.c line 70
Quoted 8 lines
drivers/net/forcedeth.c +1
-1@@ -64,7 +64,7 @@#include <asm/uaccess.h> #include <asm/system.h> -#if 0 +#if 1 #define dprintk printk#else #define dprintk(x...) do { } while (0)
The box is not even able to boot up, so many messages are printed.
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash",
In reply to Herbert XuHerbert Xu wrote, On 03/25/2009 01:26 PM:
Quoted 8 lines · Ingo Molnar
Quoted 2 lines
ok - i have started testing the delta below, on top of the plain revert.
Thanks! BTW Ingo, any chance you could help us identify the problem with the previous patch? I don't have a forcedeth machine here and the hang you had with my patch that open-coded
__napi_completeappears intimately connected to forcedeth (with NAPI enabled).
Of course it's too late for verifying this now, but (for the future) I think, this scenario could be considered:
process_backlog() netif_rx()
if (!skb)local_irq_enable()
if (queue.qlen) //NO napi_schedule() //NOTHING __skb_queue_tail() //qlen > 0
napi_complete()
... ...
Every next netif_rx() sees qlen > 0, so napi is never scheduled again.
Then, something like this might work...
Jarek P.
--- (2.6.29)
net/core/dev.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-)
net/core/dev.c +5 -1
@@ -2589,7 +2589,11 @@ static int process_backlog(struct napi_struct *napi, int quota) skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) {local_irq_enable (); -napi_complete (napi); +napi_gro_flush (napi); +local_irq_disable (); +if (skb_queue_empty (&queue->input_pkt_queue)) +__napi_complete (napi); +local_irq_enable (); goto out; }local_irq_enable ();
David Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: Jarek Poplawski <[email protected]>
Date: Wed, 25 Mar 2009 23:54:56 +0100
Quoted 21 lines
Herbert Xu wrote, On 03/25/2009 01:26 PM:
Quoted 8 lines · Ingo Molnar
Quoted 2 lines
ok - i have started testing the delta below, on top of the plain revert.
Thanks! BTW Ingo, any chance you could help us identify the problem with the previous patch? I don't have a forcedeth machine here and the hang you had with my patch that open-coded
__napi_completeappears intimately connected to forcedeth (with NAPI enabled).Of course it's too late for verifying this now, but (for the future) I think, this scenario could be considered:
process_backlog()netif_rx()if (!skb)
local_irq_enable()if (queue.qlen) //NO napi_schedule() //NOTHING __skb_queue_tail() //qlen > 0
Quoted 7 lines
napi_complete()
... ...
Every nextnetif_rx()sees qlen > 0, so napi is never scheduled again.Then, something like this might work...
Excellent detective work, I would have never figured this one out.
Herbert can you take a good look at this can confirm Jarek's findings?
Thanks!
David Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
In reply to Jarek PoplawskiFrom: Jarek Poplawski <[email protected]>
Date: Wed, 25 Mar 2009 23:54:56 +0100
Ingo, in case it isn't completely obvious, it would be wonderful if you could try Jarek's patch below with your test case.
Thanks!
Quoted 51 lines
Herbert Xu wrote, On 03/25/2009 01:26 PM:
Quoted 8 lines · Ingo Molnar
Quoted 2 lines
ok - i have started testing the delta below, on top of the plain revert.
Thanks! BTW Ingo, any chance you could help us identify the problem with the previous patch? I don't have a forcedeth machine here and the hang you had with my patch that open-coded
__napi_completeappears intimately connected to forcedeth (with NAPI enabled).Of course it's too late for verifying this now, but (for the future) I think, this scenario could be considered:
process_backlog()netif_rx()if (!skb)
local_irq_enable()if (queue.qlen) //NO napi_schedule() //NOTHING __skb_queue_tail() //qlen > 0
napi_complete()
... ...
Every nextnetif_rx()sees qlen > 0, so napi is never scheduled again.Then, something like this might work...
Jarek P.
--- (2.6.29)net/core/dev.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-)net/core/dev.c +5
-1@@ -2589,7 +2589,11 @@ static int process_backlog(struct napi_struct *napi, int quota) skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) {local_irq_enable (); -napi_complete (napi); +napi_gro_flush (napi); +local_irq_disable (); +if (skb_queue_empty (&queue->input_pkt_queue)) +__napi_complete (napi); +local_irq_enable (); goto out; }local_irq_enable ();
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 8 lines · David Miller
From: Jarek Poplawski <[email protected]>
Date: Wed, 25 Mar 2009 23:54:56 +0100Ingo, in case it isn't completely obvious, it would be wonderful if you could try Jarek's patch below with your test case.
Thanks!
David, of course testing my patch would be very nice, but I think we should definitely & immediately have this tested already Herbert's revert patch in -stable now.
Thanks,
Jarek P.
Quoted 52 lines
Quoted 52 lines
Herbert Xu wrote, On 03/25/2009 01:26 PM:
Quoted 8 lines · Ingo Molnar
Quoted 2 lines
ok - i have started testing the delta below, on top of the plain revert.
Thanks! BTW Ingo, any chance you could help us identify the problem with the previous patch? I don't have a forcedeth machine here and the hang you had with my patch that open-coded
__napi_completeappears intimately connected to forcedeth (with NAPI enabled).Of course it's too late for verifying this now, but (for the future) I think, this scenario could be considered:
process_backlog()netif_rx()if (!skb)
local_irq_enable()if (queue.qlen) //NO napi_schedule() //NOTHING __skb_queue_tail() //qlen > 0
napi_complete()
... ...
Every nextnetif_rx()sees qlen > 0, so napi is never scheduled again.Then, something like this might work...
Jarek P.
--- (2.6.29)net/core/dev.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-)net/core/dev.c +5
-1@@ -2589,7 +2589,11 @@ static int process_backlog(struct napi_struct *napi, int quota) skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) {local_irq_enable (); -napi_complete (napi); +napi_gro_flush (napi); +local_irq_disable (); +if (skb_queue_empty (&queue->input_pkt_queue)) +__napi_complete (napi); +local_irq_enable (); goto out; }local_irq_enable ();
David Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: Jarek Poplawski <[email protected]>
Date: Thu, 26 Mar 2009 06:43:17 +0000
Quoted 8 lines · David Miller
Quoted 7 lines
From: Jarek Poplawski <[email protected]>
Date: Wed, 25 Mar 2009 23:54:56 +0100Ingo, in case it isn't completely obvious, it would be wonderful if you could try Jarek's patch below with your test case.
Quoted 5 lines
Quoted 1 line
Thanks!
David, of course testing my patch would be very nice, but I think we should definitely & immediately have this tested already Herbert's revert patch in -stable now.
Sure, I'll do that.
We can toy with this thing during 2.6.30 development.
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 13 lines · David Miller
From: Jarek Poplawski <[email protected]>
Date: Thu, 26 Mar 2009 06:43:17 +0000Quoted 10 lines · David Miller
Quoted 8 lines
From: Jarek Poplawski <[email protected]>
Date: Wed, 25 Mar 2009 23:54:56 +0100Ingo, in case it isn't completely obvious, it would be wonderful if you could try Jarek's patch below with your test case.
Thanks!
Quoted 7 lines
Quoted 3 lines
David, of course testing my patch would be very nice, but I think we should definitely & immediately have this tested already Herbert's revert patch in -stable now.
Sure, I'll do that.
We can toy with this thing during 2.6.30 development.
Or add this to the next -stable after testing.
Jarek P.
Re: Revert "gro: Fix legacy path napi_complete crash",
In reply to Jarek PoplawskiQuoted 11 lines · Jarek Poplawski
Of course it's too late for verifying this now, but (for the future) I think, this scenario could be considered:
process_backlog()netif_rx()if (!skb)
local_irq_enable()if (queue.qlen) //NO napi_schedule() //NOTHING __skb_queue_tail() //qlen > 0
Quoted 7 lines
napi_complete()
... ...
Every nextnetif_rx()sees qlen > 0, so napi is never scheduled again.Then, something like this might work...
Yes this is why my original patch that started all this is broken. However, this doesn't apply to my patch that open-codes __napi_complete.
Quoted 10 lines
Jarek P.
--- (2.6.29)net/core/dev.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-)net/core/dev.c +0
-0
net/core/dev.c static int process_backlog(struct napi_struct *napi, int quota) · line 2596
Quoted 9 lines
net/core/dev.c +5
-1@@ -2589,7 +2589,11 @@ static int process_backlog(struct napi_struct *napi, int quota) skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) {local_irq_enable (); -napi_complete (napi); +napi_gro_flush (napi); +local_irq_disable (); +if (skb_queue_empty (&queue->input_pkt_queue)) +__napi_complete (napi); +local_irq_enable ();
This should work too. However, the fact that the following patch is broken means that we have bigger problems.
net: Fix netpoll lockup in legacy receive path
When I fixed the GRO crash in the legacy receive path I used napi_complete to replace __napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling __napi_complete at all.
What's more, we really do need to keep the __napi_complete call within the IRQ-off section since in theory an IRQ can occur in between and fill up the backlog to the maximum, causing us to lock up.
This patch fixes this by essentially open-coding __napi_complete.
Note we no longer need the memory barrier because this function is per-cpu.
net/core/dev.c +3 -3
@@ -2588,9 +2588,10 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +list_del (&napi->poll_list); +clear_bit (NAPI_STATE_SCHED , &napi->state);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();
@@ -2599,7 +2600,6 @@ static int process_backlog(struct napi_struct *napi, int quota)napi_gro_flush (napi); -out:return work; }
Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtDavid Miller
maintainerRe: Revert "gro: Fix legacy path napi_complete crash",
From: Herbert Xu <[email protected]>
Date: Thu, 26 Mar 2009 10:41:29 +0800
Quoted 18 lines · Jarek Poplawski
Quoted 17 lines
Of course it's too late for verifying this now, but (for the future) I think, this scenario could be considered:
process_backlog()netif_rx()if (!skb)
local_irq_enable()if (queue.qlen) //NO napi_schedule() //NOTHING __skb_queue_tail() //qlen > 0
napi_complete()
... ...
Every nextnetif_rx()sees qlen > 0, so napi is never scheduled again.
Quoted 4 lines
Quoted 1 line
Then, something like this might work...
Yes this is why my original patch that started all this is broken. However, this doesn't apply to my patch that open-codes
__napi_complete.
There is still a difference compared to your fix Herbert. Jarek's patch flushes GRO first before the unlink.
I still believe that's critical, although like you I can't pinpoint why.
I know that GRO ought to be disabled here, but what if for some reason it isn't? :-)
Adam Richter has successfully tested Jarek's variant, and if Ingo's tests show that it makes his problem go away too then I'm definitely going with Jarek's patch.
Re: Revert "gro: Fix legacy path napi_complete crash",
Quoted 9 lines · David Miller
There is still a difference compared to your fix Herbert. Jarek's patch flushes GRO first before the unlink.
I still believe that's critical, although like you I can't pinpoint why.
I know that GRO ought to be disabled here, but what if for some reason it isn't? :-)
Sure, I can accept that somehow someone has enabled GRO :) But I'd still like to know why flushing the GRO afterwards would lead to a hang.
Quoted 3 lines
Adam Richter has successfully tested Jarek's variant, and if Ingo's tests show that it makes his problem go away too then I'm definitely going with Jarek's patch.
I don't have a problem with that.
I've asked Adam to test my patch as well. So far the only failure case against it has been on Ingo's machine, where the process_backlog path isn't involved. Yes it's used for loopback, but he's seeing the hang on eth0, which with that config uses netif_receive_skb so it should continue to work even if process_backlog completely seizes up.
Cheers,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txtJarek Poplawski
Tested-by Adam RichterRe: Revert "gro: Fix legacy path napi_complete crash",
In reply to David MillerOn Wed, Mar 25, 2009 at 08:20:50PM -0700, David Miller wrote:
...
Quoted 3 lines
Adam Richter has successfully tested Jarek's variant, and if Ingo's tests show that it makes his problem go away too then I'm definitely going with Jarek's patch.
I hope this patch version on top of Herbert's revert could be useful then.
Thanks,
Jarek P.
-------------------->
GRO: Re-enable GRO on legacy netif_rx path.
Replacing __napi_complete() with napi_complete() in process_backlog() caused various breaks for non-napi NICs. It looks like the following scenario can happen:
process_backlog() netif_rx()
if (!skb)local_irq_enable()
if (queue.qlen) //NO napi_schedule() //NOTHING __skb_queue_tail() //qlen > 0
napi_complete()
... ...
Every next netif_rx() sees qlen > 0, so napi is never scheduled again.
This patch fixes it by open-coding napi_complete() with additional check for empty queue before __napi_complete().
With help of debugging by Ingo Molnar, Sascha Hauer and Herbert Xu.
---
(vs. 2.6.29 with Herbert's "GRO: Disable GRO on legacy netif_rx path")
net/core/dev.c +10 -3
@@ -2588,15 +2588,22 @@ static int process_backlog(struct napi_slocal_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { -__napi_complete (napi);local_irq_enable (); -break ; +napi_gro_flush (napi); +local_irq_disable (); +if (skb_queue_empty (&queue->input_pkt_queue)) +__napi_complete (napi); +local_irq_enable (); + goto out; }local_irq_enable (); -netif_receive_skb (skb); +napi_gro_receive (napi, skb); }while (++work < quota && jiffies == start_time); +napi_gro_flush (napi); + +out:return work; }
Re: Revert "gro: Fix legacy path napi_complete crash",
In reply to Herbert XuOn Thu, Mar 26, 2009 at 10:41:29AM +0800, Herbert Xu wrote:
...
Quoted 2 lines
Yes this is why my original patch that started all this is broken. However, this doesn't apply to my patch that open-codes
__napi_complete.
...
Quoted 2 lines
This should work too. However, the fact that the following patch is broken means that we have bigger problems.
I agree. This should be effectively equal to the revert, so I guess Ingo probably hit some other bug btw.
Jarek P.
Quoted 51 lines
net: Fix netpoll lockup in legacy receive path
When I fixed the GRO crash in the legacy receive path I used
napi_completeto replace__napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling__napi_completeat all.What's more, we really do need to keep the
__napi_completecall within the IRQ-off section since in theory an IRQ can occur in between and fill up the backlog to the maximum, causing us to lock up.This patch fixes this by essentially open-coding
__napi_complete.Note we no longer need the memory barrier because this function is per-cpu.
Signed-off-by Herbert Xu <[email protected]>net/core/dev.c +3
-3@@ -2588,9 +2588,10 @@ static int process_backlog(struct napi_struct *napi, int quota)local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue);if (!skb) { +list_del (&napi->poll_list); +clear_bit (NAPI_STATE_SCHED , &napi->state);local_irq_enable (); -napi_complete (napi); - goto out; +break ; }local_irq_enable ();@@ -2599,7 +2600,6 @@ static int process_backlog(struct napi_struct *napi, int quota)napi_gro_flush (napi); -out:return work; }Thanks,
Signature · 4 lines
Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[email protected]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Revert "gro: Fix legacy path napi_complete crash",
In reply to Herbert XuFrom: Herbert Xu <[email protected]>
Date: Wed, 25 Mar 2009 20:08:40 +0800
Quoted 12 lines
GRO: Disable GRO on legacy
netif_rxpathWhen I fixed the GRO crash in the legacy receive path I used
napi_completeto replace__napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling__napi_completeat all.What's more, we really do need to keep the
__napi_completecall within the IRQ-off section since in theory an IRQ can occur in between and fill up the backlog to the maximum, causing us to lock up.
Quoted 4 lines
Since we can't seem to find a fix that works properly right now, this patch reverts all the GRO support from the
netif_rxpath.Signed-off-by Herbert Xu <[email protected]>
Applied, and will push to -stable.
Re: Revert "gro: Fix legacy path napi_complete crash",
In reply to Herbert XuQuoted 7 lines · Herbert Xu
Quoted 3 lines · David Miller
I think the problem is that we need to do the GRO flush before the list delete and clearing the
NAPI_STATE_SCHEDbit.Well first of all GRO shouldn't even be on in Ingo's case, unless he enabled it by hand with ethtool. [...]
i didnt. (But it's randconfig - so please have a good look at all .config details - maybe something has an unexpected side-effect?)
Ingo
Re: Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux 2.6.29)
In reply to Ingo MolnarHi Ingo,
Quoted 15 lines · Ingo Molnar
Quoted 12 lines · Robert Schwebel
Quoted 10 lines · Ingo Molnar
If the box hung within 15 minutes, the kernel was deemed bad. Using that method i arrived to this upstream networking fix which was merged yesterday:
| 303c6a0251852ecbdc5c15e466dcaff5971f7517 is first bad commit | commit 303c6a0251852ecbdc5c15e466dcaff5971f7517 | Author: Herbert Xu <[email protected]> | Date: Tue Mar 17 13:11:29 2009 -0700 | | gro: Fix legacy path napi_complete crash
Quoted 5 lines
Quoted 2 lines
This commit breaks nfsroot booting on i.MX27 and other ARM boxes with different network cards here in a reproducable way.
Can you confirm that Herbert's fix (see it below) solves the problem?
No, still doesn't work.
It seems to have something to do with enabling interrupts between __skb_dequeue() and __napi_complete().
I reverted 303c6a0251852ecbdc5c15e466dcaff5971f7517 and added a
local_irq_enable(); local_irq_disable();
right before __napi_complete() and this already breaks networking.
Sascha
Quoted 68 lines
Ingo
--------------->
Fromb8b66ac07cab1b45aac93e4f406833a1e0d7677eMon Sep 17 00:00:00 2001
From: Herbert Xu <[email protected]>
Date: Tue, 24 Mar 2009 21:35:42 +0800
Subject: [PATCH] net: Fix netpoll lockup in legacy receive pathWhen I fixed the GRO crash in the legacy receive path I used
napi_completeto replace__napi_complete. Unfortunately they're not the same when NETPOLL is enabled, which may result in us not calling__napi_completeat all.While this is fishy in itself, let's make the obvious fix right now of reverting to the previous state where we always called
__napi_complete.Signed-off-by Herbert Xu <[email protected]>Cc Linus Torvalds <[email protected]>Cc Frank Blaschka <[email protected]>Cc "David S. Miller" <[email protected]>Cc Peter Zijlstra <[email protected]>LKML-Reference: <[email protected]>
Signed-off-by Ingo Molnar <[email protected]>--- net/core/dev.c | 16 +++++++++------- 1 files changed, 9 insertions(+), 7 deletions(-)net/core/dev.c +9
-7@@ -2580,24 +2580,26 @@ static int process_backlog(struct napi_struct *napi, int quota)int work =0 ;struct softnet_data *queue = &__get_cpu_var (softnet_data);unsigned long start_time = jiffies; +struct sk_buff *skb; napi->weight = weight_p;do { -struct sk_buff *skb; -local_irq_disable (); skb =__skb_dequeue (&queue->input_pkt_queue); -if (!skb) { -local_irq_enable (); -napi_complete (napi); - goto out; - }local_irq_enable (); +if (!skb) +break ;napi_gro_receive (napi, skb); }while (++work < quota && jiffies == start_time);napi_gro_flush (napi); +if (skb) + goto out; + +local_irq_disable (); +__napi_complete (napi); +local_irq_enable (); out:return work;
Signature · 4 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Am Dienstag, 24. März 2009 schrieb Linus Torvalds:
Quoted 3 lines
This obviously starts the merge window for 2.6.30, although as usual, I'll probably wait a day or two before I start actively merging.
It would be very nice, if you could start with a commit to Makefile, that reflects the new series: e.g.:
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 30
EXTRAVERSION = -pre
-pre for preparing state.
Thanks,
Pete
Quoted 7 lines · Hans-Peter Jansen
Am Dienstag, 24. März 2009 schrieb Linus Torvalds:
Quoted 2 lines
This obviously starts the merge window for 2.6.30, although as usual, I'll probably wait a day or two before I start actively merging.
It would be very nice, if you could start with a commit to
Makefile, that reflects the new series: e.g.:
Quoted 6 lines
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 30
EXTRAVERSION = -pre-pre for preparing state.
If you're using the kernel-of-they-day, you're probably using git, and CONFIG_LOCALVERSION_AUTO=y should be mandatory.
My kernel is called 2.6.29-03321-gbe0ea69...
With kind regards,
Geert Uytterhoeven
Software Architect
Sony Techsoft Centre Europe
The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium
Phone: +32 (0)2 700 8453 Fax: +32 (0)2 700 8622 E-mail: [email protected] Internet: http://www.sony-europe.com/
A division of Sony Europe (Belgium) N.V.
VAT BE 0413.825.160 · RPR Brussels
Fortis · BIC GEBABEBB · IBAN BE41293037680010
Quoted 13 lines · Geert Uytterhoeven
Quoted 12 lines · Hans-Peter Jansen
Am Dienstag, 24. März 2009 schrieb Linus Torvalds:
Quoted 2 lines
This obviously starts the merge window for 2.6.30, although as usual, I'll probably wait a day or two before I start actively merging.
It would be very nice, if you could start with a commit to
Makefile, that reflects the new series: e.g.:VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 30
EXTRAVERSION = -pre
Quoted 4 lines
Quoted 1 line
-pre for preparing state.
If you're using the kernel-of-they-day, you're probably using git, and
CONFIG_LOCALVERSION_AUTO=yshould be mandatory.
I sure hope it never becomes mandatory, I despise that thing. I don't even do -rc tags. .nn is .nn until baked and nn.1 appears.
(would be nice if baked were immediately handed to stable .nn.0 instead of being in limbo for a bit, but I don't drive the cart, just tag along behind [w. shovel];)
-Mike
Quoted 6 lines · Mike Galbraith
Quoted 3 lines
If you're using the kernel-of-they-day, you're probably using git, and
CONFIG_LOCALVERSION_AUTO=yshould be mandatory.I sure hope it never becomes mandatory, I despise that thing. I don't even do -rc tags. .nn is .nn until baked and nn.1 appears.
If you're a git user that changes kernels frequently, then enabling CONFIG_LOCALVERSION_AUTO is _really_ convenient when you learn to use it.
This is quite common for me:
gitk v$(uname -r)..
and it works exactly due to CONFIG_LOCALVERSION_AUTO (and because git is rather good at figuring out version numbers). It's a great way to say "ok, what is in my git tree that I'm not actually running right now".
Another case where CONFIG_LOCALVERSION_AUTO is very useful is when you're noticing some new broken behavior, but it took you a while to notice. You've rebooted several times since, but you know it worked last Tuesday. What do you do?
The thing to do is
grep "Linux version" /var/log/messages*
and figure out what the good version was, and then do
git bisect start
git bisect good ..that-version..
git bisect bad v$(uname -r)
and off you go. This is _very_ convenient if you are working with some "random git kernel of the day" like I am (and like hopefully others are too, in order to get test coverage).
Quoted 3 lines
(would be nice if baked were immediately handed to stable .nn.0 instead of being in limbo for a bit, but I don't drive the cart, just tag along behind [w. shovel];)
Note that the "v2.6.29[-rcX" part is totally _useless_ in many cases, because if you're working past merges, and especially if you end up doing bisection, it is very possible that the main Makefile says "2.6.28-rc2", but the code you're working on wasn't actually _merged_ until after 2.6.29.
In other words, the main Makefile version is totally useless in non-linear development, and is meaningful _only_ at specific release times. In between releases, it's essentially a random thing, since non-linear development means that versioning simply fundamentally isn't some simple monotonic numbering. And this is exactly when CONFIG_LOCALVERSION_AUTO is a huge deal.
(It's even more so if you end up looking at "next" or merging other peoples trees. If you only ever track my kernel, and you only ever fast-forward - no bisection, no nothing - then the release numbering looks "simple", and things like LOCALVERSION looks just like noise).
Linus
Quoted 31 lines · Linus Torvalds
Quoted 6 lines · Mike Galbraith
Quoted 3 lines
If you're using the kernel-of-they-day, you're probably using git, and
CONFIG_LOCALVERSION_AUTO=yshould be mandatory.I sure hope it never becomes mandatory, I despise that thing. I don't even do -rc tags. .nn is .nn until baked and nn.1 appears.
If you're a git user that changes kernels frequently, then enabling
CONFIG_LOCALVERSION_AUTOis _really_ convenient when you learn to use it.This is quite common for me:
gitk v$(uname -r)..and it works exactly due to
CONFIG_LOCALVERSION_AUTO(and because git is rather good at figuring out version numbers). It's a great way to say "ok, what is in my git tree that I'm not actually running right now".Another case where
CONFIG_LOCALVERSION_AUTOis very useful is when you're noticing some new broken behavior, but it took you a while to notice. You've rebooted several times since, but you know it worked last Tuesday. What do you do?The thing to do is
grep "Linux version"
/var/log/messages*and figure out what the good version was, and then do
Quoted 7 lines
git bisect start
git bisect good ..that-version..
git bisect bad v$(uname -r)and off you go. This is _very_ convenient if you are working with some "random git kernel of the day" like I am (and like hopefully others are too, in order to get test coverage).
That's why it irritates me. I build/test a lot, and do the occasional bisection, which makes a mess in /boot and /lib/modules. I use a quilt stack of git pull diffs as reference/rummage points. Awkward maybe, but effective (so no need for autoversion), and no mess.
-Mike
Am Freitag, 27. März 2009 schrieb Linus Torvalds:
Quoted 6 lines
In other words, the main
Makefileversion is totally useless in non-linear development, and is meaningful _only_ at specific release times. In between releases, it's essentially a random thing, since non-linear development means that versioning simply fundamentally isn't some simple monotonic numbering. And this is exactly whenCONFIG_LOCALVERSION_AUTOis a huge deal.
Well, you guys always see things from a deeply involved kernel developer _using git_ POV - which I do understand and accept (unlike hats nobody can change his head after all ;-), but there are other approaches to kernel source code, e.g. git is also really great for tracking the kernel development without any further involvement apart from using the resulting trees.
I build kernel rpms from your git tree, and have a bunch of BUILDs lying around. Sure, I can always fetch the tarballs or fiddle with git, but why? Having a Makefile start commit allows to make sure with simplest tools, say "head Makefile" that a locally copied 2.6.29 tree is really a 2.6.29, and not something moving towards the next release. That's all, nothing less, nothing more, it's just a strong hint which blend is in the box.
I always wonder, why Arjan does not intervene for his kerneloops.org project, since your approach opens a window of uncertainty during the merge window when simply using git as an efficient fetch tool.
Ducks and hides now,
Pete
Quoted 3 lines · Hans-Peter Jansen
Am Freitag, 27. März 2009 schrieb Linus Torvalds:
I always wonder, why Arjan does not intervene for his kerneloops.org project, since your approach opens a window of uncertainty during the merge window when simply using git as an efficient fetch tool.
I would *love* it if Linus would, as first commit mark his tree as "-git0" (as per snapshots) or "-rc0". So that I can split the "final" versus "merge window" oopses.
Quoted 10 lines · Arjan van de Ven
Quoted 5 lines · Hans-Peter Jansen
Am Freitag, 27. März 2009 schrieb Linus Torvalds:
I always wonder, why Arjan does not intervene for his kerneloops.org project, since your approach opens a window of uncertainty during the merge window when simply using git as an efficient fetch tool.
I would *love* it if Linus would, as first commit mark his tree as "-git0" (as per snapshots) or "-rc0". So that I can split the "final" versus "merge window" oopses.
FWIW, that would also be useful for tracking regressions.
Thanks,
Rafael
Am Dienstag, 31. März 2009 schrieb Arjan van de Ven:
Quoted 9 lines
Quoted 4 lines · Hans-Peter Jansen
I always wonder, why Arjan does not intervene for his kerneloops.org project, since your approach opens a window of uncertainty during the merge window when simply using git as an efficient fetch tool.
I would *love* it if Linus would, as first commit mark his tree as "-git0" (as per snapshots) or "-rc0". So that I can split the "final" versus "merge window" oopses.
..which is an important difference. I still vote for -pre for "preparation state" as -git0 does imply some sort of versioning, which *is* meaningless in this state.
Linus, this would be a small step for you, but makes a big difference for those of us, that miss it sorely.
Junio: is it possible to automate this in git somehow: make sure, that the first commit after a release really happens for a "new" version (e.g. a version patch to Makefile)?
Pete
Quoted 8 lines · Arjan van de Ven
Quoted 3 lines · Hans-Peter Jansen
Am Freitag, 27. März 2009 schrieb Linus Torvalds:
I always wonder, why Arjan does not intervene for his kerneloops.org project, since your approach opens a window of uncertainty during the merge window when simply using git as an efficient fetch tool.
I would *love* it if Linus would, as first commit mark his tree as "-git0" (as per snapshots) or "-rc0". So that I can split the "final" versus "merge window" oopses.
Can't you discern that from the v$VERSION tag? According to your definition, -git0 would simply be v2.6.29 commit + 1, correct?
Jeff
Quoted 11 lines · Jeff Garzik
Quoted 8 lines · Arjan van de Ven
Quoted 3 lines · Hans-Peter Jansen
Am Freitag, 27. März 2009 schrieb Linus Torvalds:
I always wonder, why Arjan does not intervene for his kerneloops.org project, since your approach opens a window of uncertainty during the merge window when simply using git as an efficient fetch tool.
I would *love* it if Linus would, as first commit mark his tree as "-git0" (as per snapshots) or "-rc0". So that I can split the "final" versus "merge window" oopses.
Can't you discern that from the v$VERSION tag? According to your definition, -git0 would simply be v2.6.29 commit + 1, correct?
it needs to be something that is shown in the oops output... ... basically version or extraversion in the Makefile.
Hi!
Quoted 7 lines
Quoted 3 lines
I always wonder, why Arjan does not intervene for his kerneloops.org project, since your approach opens a window of uncertainty during the merge window when simply using git as an efficient fetch tool.
I would *love* it if Linus would, as first commit mark his tree as "-git0" (as per snapshots) or "-rc0". So that I can split the "final" versus "merge window" oopses.
Pretty please... I keep kernel binaries around and being able to tell
what it is when it boots is useful.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 2 lines · On 31.03.2009 00:00 Hans-Peter Jansen wrote:
I build kernel rpms from your git tree, and have a bunch of BUILDs lying around.
So you have a place where you have a git repository from which you copy the source tree to rpms, which have no connection to the git anymore?
Quoted 1 line
Sure, I can always fetch the tarballs or fiddle with git, but why?
You may add a small script like this into .git/hooks/post-checkout:
-----
#!/bin/bash
if [ "$3" == 1 ]; then # don't do it for file checkouts
sed -ri "s/^(EXTRAVERSION =.*)/\1$(scripts/setlocalversion)/" Makefile
fi
-----
That will append the EXTRAVERSION automatically with what CONFIG_LOCALVERSION_AUTO=y would append to the version string.
Quoted 4 lines
Having a
Makefilestart commit allows to make sure with simplest tools, say "headMakefile" that a locally copied 2.6.29 tree is really a 2.6.29, and not something moving towards the next release. That's all, nothing less, nothing more, it's just a strong hint which blend is in the box.
If you are working on a tagged version, the EXTRAVERSION won't be extended, on an untagged version it will have some ident for that intermediate version
e.g.
git checkout master -> EXTRAVERSION =-07100-g833bb30 git checkout HEAD~1 -> EXTRAVERSION =-07099-g8b53ef3 git checkout v2.6.29 -> EXTRAVERSION = git checkout HEAD~1 -> EXTRAVERSION = -rc8-00303-g0030864 git checkout v2.6.29-rc8 -> EXTRAVERSION = -rc8
In that way your copies of the source tree will have the EXTRAVERSION set in the Makefile. You can detect an intermediate version easily in the Makefile and you even can checkout that exact version from the git tree later, if you need to. Or just make an diff between two rpms by diffing the versions taken from the Makefiles e.g.
git diff 07099-g8b53ef3..07100-g833bb30
or
git diff 00303-g0030864..v2.6.29
Attention:
Of course, the Makefile is changed in your working tree as if you had changed it yourself. Therefore you have to use "git checkout Makefile" to revert the changes before you can checkout a different version from the git tree.
This is only a hack and there might be a better way to do it, but maybe it helps as a starting point in your special situation.
Andreas
Quoted 6 lines · Hans-Peter Jansen
Am Dienstag, 24. März 2009 schrieb Linus Torvalds:
Quoted 2 lines
This obviously starts the merge window for 2.6.30, although as usual, I'll probably wait a day or two before I start actively merging.
It would be very nice, if you could start with a commit to
Makefile, that reflects the new series: e.g.:
If you have a git checkout, you can easily do this yourself:
git checkout -b 2.6.30-rc master
sed -i "/^SUBLEVEL/ s/29/30/; /^EXTRAVERSION/ s/$/ -rc0/" Makefile git add Makefile
git commit -m "Mark as -rc0"
Then to get latest git head:
git checkout master
git pull
git rebase master 2.6.30-rc
When Linus releases -rc1, the rebase will signal a conflict on that commit and you can just 'git rebase --skip' it.
Instead of sed you can also just edit the Makefile of course, or you can go the other way and create a simple script that automatically increases the existing sublevel by 1. I just do this manually, given that it's only needed once per three months or so.
Using a branch is something I do anyway as I almost always have a few minor patches on top of git head for various reasons.
Cheers,
FJP